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.

Sign up for GitHub

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
Merged

Update major release guidance #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 12 additions & 14 deletions pmix_governance.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -529,21 +529,19 @@ \subsubsection{Release Managers}%
the community mailing list. Minor releases, therefore, can occur on an
at most a quarterly basis.

Major release candidates must be approved during the ASC's annual
face-to-face meeting. Release Managers must notify the Co-Chairs of a
major release candidate a minimum of two quarters before the target
approval meeting. The Co-Chairs will add an item to the agenda of each
quarterly meeting for discussion and review of the document, and on the
face-to-face meeting for vote on final approval. Once the ASC has voted
its approval, the Release Managers shall post the new release on the
community's web site and send an email announcing the release to the
community mailing list. Should the ASC not approve the release,
subsequent release candidates can be considered at upcoming regular ASC
meetings - i.e., the major release candidate does not have to wait for
the next annual face-to-face meeting for reconsideration. However, no
Major release candidates can be approved during any ASC quarterly
meeting. Release Managers must notify the Co-Chairs of a major release
candidate a minimum of two quarters before the target approval
meeting. The Co-Chairs will add an item to the agenda of each quarterly
meeting for discussion and review of the document, and on the target
meeting for vote on final approval. Once the ASC has voted its approval,
the Release Managers shall post the new release on the community's web
site and send an email announcing the release to the community mailing
list. Should the ASC not approve the release, subsequent release
candidates can be considered at upcoming ASC meetings. Note, no
subsequent major release may begin the approval process until after the
current candidate has been published. Major releases, therefore, can
occur no more than once per year.
current candidate has been published. Major releases shall not occur
more than once per year.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Expand Down