You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 (regardless of when this issue was opened):
No open issues or PRs in the module that would require breaking changes
No TODOs in the module code that would require breaking changes
This is very new package. Should be considered experimental for now. I don't think it's ready for 1.0. I would suggest holding off on this one and focus on other modules for now
Would this actually be used in the Collector v1 distribution we are working on #9375? (I just want to clarify if this should be prioritized by the Collector Stability Working Group or not)
Would this actually be used in the Collector v1 distribution we are working on #9375? (I just want to clarify if this should be prioritized by the Collector Stability Working Group or not)
Looks like it's not. It's currently being used by scraping receivers only. I'd suggest we wait for broader adoption of this module before declaring it 1.0. k8sattributes and docker receiver have config parts that should adopt it first
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 (regardless of when this issue was opened):
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: