TC Review Request: (API / SDK / Collector-module)
January 27, 2026 · View on GitHub
1. Review scope
| Signal | Part of project | Current maturity | Target maturity |
|---|---|---|---|
| <Tracing | Metrics | Logs | Profiles> | <API / SDK package / Other> | experimental / beta | stable |
2. Motivation
<Why are you requesting stability now? Adoption stats, user demand, risk mitigation, etc.>
3. Target version / tag
<org>/<repo>@<tag> – commit <sha>
4. Links for reviewers
- Spec compliance matrix:
- Public docs / getting-started sample:
- CHANGELOG draft:
5. Self-checklist
- I understand the TC review process and commit to being responsive to any requests for assistance and to issues opened during the review.
- All MUST / MUST NOT requirements implemented
- Spec compliance matrix populated and up-to-date
- Docs & examples updated
- Test suites passing
- CHANGELOG prepared
6. Maintainer points-of-contact
- @
– SIG lead / primary contact - @
– backup
7. Requested reviewer expertise
<e.g., "Metrics SDK spec", "Collector pipeline", "Logs data-model">
/cc @open-telemetry/technical-committee