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

Update major release guidance #35

Merged
merged 1 commit into from
May 12, 2022

Conversation

raffenet
Copy link
Contributor

Remove face-to-face meeting requirement for major release approval, and
updating surrounding text. Retain limit of one major release per year.

Remove face-to-face meeting requirement for major release approval, and
updating surrounding text. Retain limit of one major release per year.

Signed-off-by: Ken Raffenetti <[email protected]>
@raffenet raffenet force-pushed the major-release-guidance branch from f71a42d to 1aecaad Compare November 15, 2021 19:17
@raffenet
Copy link
Contributor Author

Here's my stab at updating the major release guidance. Please give your feedback!
cc: @dsolt

Copy link

@dsolt dsolt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me.

@kathrynmohror
Copy link
Collaborator

Please use emoji reactions ON THIS COMMENT to indicate your position on this proposal.

  • You do not need to vote on every proposal
  • If you have no opinion, don't vote - that is also useful data
  • If you've already commented on this issue, please still vote so
    we know your current thoughts
  • Not all proposals solve exactly the same problem, so we may end
    up accepting proposals that appear to have some overlap
    This is not a binding majority-rule vote, but it will be a very
    significant input into the corresponding ASC decision.

Here are the meanings for the emojis:

  • Hooray or Rocket: I support this so strongly that I
    want to be an advocate for it
  • Heart: I think this is an ideal solution
  • Thumbs up: I'd be happy with this solution
  • Confused: I'd rather we not do this, but I can tolerate it
  • Thumbs down: I'd be actively unhappy, and may even consider
    other technologies instead
    If you want to explain in more detail, feel free to add another
    comment, but please also vote on this comment.

@jjhursey jjhursey added the Proposed Ready for review label Nov 23, 2021
@jjhursey jjhursey added Governance Modification to governance rules Eligible Eligible for consideration by ASC labels Jan 13, 2022
@jjhursey
Copy link
Member

jjhursey commented Mar 7, 2022

PMIx ASC 1Q 2022

  • Passed the first vote: 11 yes / 0 no / 0 abstain
  • This is eligible for second vote in the 2Q 2022 ASC quarterly meeting

@jjhursey jjhursey added the First Vote Passed ASC first vote passed label Mar 7, 2022
@jjhursey
Copy link
Member

PMIx ASC 2Q 2022

  • Passed the second vote: 11 yes / 0 no / 0 abstain
  • Will be merged into the next release

@jjhursey jjhursey merged commit a168ca0 into pmix:master May 12, 2022
@jjhursey jjhursey added the Accepted ASC second vote passed. Accepted! label May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted ASC second vote passed. Accepted! Eligible Eligible for consideration by ASC First Vote Passed ASC first vote passed Governance Modification to governance rules Proposed Ready for review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants