-
Notifications
You must be signed in to change notification settings - Fork 7
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
RFC: allow major text changes to ship in minor releases #36
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor typo. Generally I think this is fine. It gives the ASC a bit more power to include descriptive items in minor releases at their discretion. Since there is already a 2 vote sequence to get things in there is plenty of time for folks to review and consider the semantic implications.
Please use emoji reactions ON THIS COMMENT to indicate your position on this proposal.
Here are the meanings for the emojis:
|
96e0143
to
d29db56
Compare
0b48215
to
3300ea7
Compare
this is a latexdiff version for those that find it easier to read. |
PMIx ASC 1Q 2022
|
PMIx ASC 2Q 2022
|
give the ASC flexibility in accepting the proposal to the next major (rather than minor) release, without pushing back the proposal. Signed-off-by: Aurélien Bouteiller <[email protected]>
Signed-off-by: Aurélien Bouteiller <[email protected]> Co-authored-by: Kathryn Mohror <[email protected]>
3300ea7
to
5ad0d60
Compare
I rebased this PR to prepare for the merge. No text changes. |
Let the PR Author decide what is the target release for their PR, and
give the ASC flexibility in accepting the proposal to the next major
(rather than minor) release, without pushing back the proposal.