Skip to content
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 configcompression #9374

Closed
8 tasks done
Tracked by #9375
TylerHelmuth opened this issue Jan 24, 2024 · 0 comments · Fixed by #9571
Closed
8 tasks done
Tracked by #9375

Stabilize module configcompression #9374

TylerHelmuth opened this issue Jan 24, 2024 · 0 comments · Fixed by #9571

Comments

@TylerHelmuth
Copy link
Member

TylerHelmuth commented Jan 24, 2024

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:

  • No open issues or PRs in the module that would require breaking changes
  • No TODOs in the module code that would require breaking changes
  • No deprecated symbols in the module
  • No symbols marked as experimental in the module
  • The module follows the Coding guidelines

Please also make sure to publicly announce our intent to stabilize the module on:

  • The #otel-collector CNCF Slack Channel
  • The #opentelemetry CNCF Slack channel
  • A Collector SIG meeting (if unable to attend, just add to the agenda)

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.

dmitryax pushed a commit that referenced this issue Mar 7, 2024
**Description:**
Mark `configcompression` as Stable

**Link to tracking Issue:** 
Closes
#9374

---------

Co-authored-by: Alex Boten <223565+codeboten@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant