-
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 confignet #9045
Comments
This is the PR to mark confignet as stable #7954 |
Open issues regarding confignet: |
I think we should have 1.0 milestones for each module that we want to release as 1.0 so we can include all the issues there |
@dmitryax created the milestone and added issues to it |
@codeboten I think it would be helpful to have links as in #8978 so that right before marking as 1.0 one can quickly check that we did not accidentally introduce any new TODOs or experimental symbols |
We need to address the new comments in #7954 as well. |
Filed #9159 to add this to coding guidelines |
Should we remove |
We discussed this offline and decided that we should |
See #9258 |
Blocked by the stabilization work for confmap |
Is this now unblocked since confmap was just declared stable? |
**Description:** Mark `confignet` as Stable **Link to tracking Issue:** Closes #9045 --------- Co-authored-by: Pablo Baeyens <pablo.baeyens@datadoghq.com> Co-authored-by: Alex Boten <223565+codeboten@users.noreply.github.com>
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: