-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stabilize module consumer #9046
Comments
|
Published intent on #otel-collector CNCF Slack Channel: |
Scheduled for SIG meeting 9am 12/19. Please feel free to attend and bring up any items for discussion, your feedback is helpful. |
I believe issues are being tracked in https://github.com/open-telemetry/opentelemetry-collector/milestone/31 |
Looks like the milestone doesn't track PRs, just issues. Do we need to reopen #8833? |
Discussed with maintainers, we can for now not reopen #8833 and keep it out of scope of the consumer 1.0 package. |
#### Description Mark `consumer` module as stable. This is now possible after open-telemetry#11491, since `consumererror` is a separate module now. #### Link to tracking issue Fixes open-telemetry#9046 Co-authored-by: Alex Boten <[email protected]>
Before stabilizing a module, an approver or maintainer must make sure that the following criteria have been met for at least two successive minor version releases:
Please also make sure to publicly announce our intent to stabilize the module on:
To help other people verify the above criteria, please link to the announcement and other links used to complete the above in a comment on this issue.
Once all criteria are met, close this issue by moving this module to the
stable
module set.The text was updated successfully, but these errors were encountered: