From caa74317fa238a575f12e82a3e0ac7cc354ba366 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Aur=C3=A9lien=20Bouteiller?= Date: Thu, 2 Dec 2021 16:04:10 -0500 Subject: [PATCH 1/2] 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. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Aurélien Bouteiller --- pmix_governance.tex | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/pmix_governance.tex b/pmix_governance.tex index 8e45cae..d6b824d 100755 --- a/pmix_governance.tex +++ b/pmix_governance.tex @@ -1237,6 +1237,10 @@ \subsubsection{Major Text Changes}% the document such as introductory text in a chapter, definitions of terms, re-organization of chapter contents or chapter placement, non-errata level changes to descriptions of APIs including advice to implementors/users. +A major text change can target an upcoming minor, or major release of the +standard, but significant changes in the semantics of existing +APIs shall target major releases. The definition of ``significant'' +is determined by the members of the ASC. The process for major text changes begins with a GitHub Draft PR while writing the proposal, optionally proceeded by a GitHub Issue for more general discussion and guidance. When the GitHub PR is ready for discussion the author(s) must remove the Draft PR status, add the ``RFC'' and ``Major Text Change'' labels, and add the Straw Poll Comment to it. @@ -1257,7 +1261,8 @@ \subsubsection{Major Text Changes}% both), or at the request of the proposal's author(s), the Co-Chairs will schedule the proposal for a reading at the next quarterly meeting of the ASC. The proposal shall be included in the announced agenda for the -meeting along with a link to the PR. +meeting along with a link to the PR. The PR shall explicitly specify if +it targets an upcoming minor or major release version of the standard. The Co-Chairs shall label the PR as ``Eligible'' to indicate that the proposal is eligible for formal consideration by the ASC at the next quarterly meeting. @@ -1283,8 +1288,8 @@ \subsubsection{Major Text Changes}% above voting rules) to determine final disposition of the proposal. The Co-Chairs shall subsequently set a GitHub label indicating the result as either ``Accepted'' or ``Pushed Back''. Accepted -proposals can be committed to the next major release version by the -Release Manager in accordance with their schedule. +proposals can be committed to the next specified target release version +by the Release Manager in accordance with their schedule. Proposals that are pushed back at any point can be modified and resubmitted by the author(s). However, the updated PR must pass through @@ -1293,7 +1298,9 @@ \subsubsection{Major Text Changes}% submitted for the identical elements but must be linked to the original PR in order to retain full information regarding prior concerns and suggestions. Alternatively, the ASC may suggest a Revision Exception vote -instead of pushing back the PR. +instead of pushing back the PR. The ASC may also suggest a Revision Exception +vote to change the target release for the PR; in this case, the PR should +be rebased on the new target release with no other changes to its history. \hypertarget{process-flow-for-major-text-changes}{% \paragraph{Process flow for Major Text Changes}% @@ -1319,6 +1326,8 @@ \subsubsection{Major Text Changes}% Remove the Draft PR status \item Label the PR ``RFC'' and ``Major Text Change'' + \item + Milestone the PR with the target (minor or major) release of the standard \item Add the Straw Poll Comment to request feedback \item @@ -1344,8 +1353,7 @@ \subsubsection{Major Text Changes}% \end{enumerate} Note that a proposal requires a minimum of two quarterly meetings to be -accepted and that actual publication of the accepted proposal must be -included in the next major release of the standard. +accepted. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% From 5ad0d60940fb77fedf772245b1c678ffa31be8c0 Mon Sep 17 00:00:00 2001 From: Aurelien Bouteiller Date: Fri, 14 Jan 2022 16:05:53 -0500 Subject: [PATCH 2/2] Update pmix_governance.tex MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Aurélien Bouteiller Co-authored-by: Kathryn Mohror --- pmix_governance.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pmix_governance.tex b/pmix_governance.tex index d6b824d..04144f8 100755 --- a/pmix_governance.tex +++ b/pmix_governance.tex @@ -1237,7 +1237,7 @@ \subsubsection{Major Text Changes}% the document such as introductory text in a chapter, definitions of terms, re-organization of chapter contents or chapter placement, non-errata level changes to descriptions of APIs including advice to implementors/users. -A major text change can target an upcoming minor, or major release of the +A major text change can target an upcoming minor or major release of the standard, but significant changes in the semantics of existing APIs shall target major releases. The definition of ``significant'' is determined by the members of the ASC.