RFC: Add release policy #3673
Draft
RFC: Add release policy #3673
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
veroandreo
reviewed
Apr 29, 2024
Contributor
veroandreo
left a comment
veroandreo
left a comment
There was a problem hiding this comment.
I know it is a draft, but while reading, I made some edit suggestions :)
Co-authored-by: Veronica Andreo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to a discussion with @veroandreo and @petrasovaa, I'm creating an RFC for a Release Policy. This is mainly derived from relevant parts of Release Schedule on Track wiki and it is different from #2815 Release Procedure and release schedule which will be part of a roadmap.
This is not ready, but feel free to comment on the content and scope.
Additional info
Whiteboard from the discussion with @veroandreo and @petrasovaa: