Fix typo in the "Elevation to Stable status" section

One paragraph claims that interfaces can be committed to the next *minor* release, and a following sentence claims that the accepted proposal must be included in the next *major* release. Change the first reference to *minor* release to *major* in order to unify these claims about when the change to "Stable" can occur. Fixes pmix#5 Signed-off-by: Stephen Herbein <[email protected]>
SteVwonder · Aug 20, 2019 · 9174b61 · 9174b61
1 parent 628fbea
commit 9174b61
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/pmix_governance.tex b/pmix_governance.tex
@@ -799,7 +799,7 @@ \subsubsection{Elevation to Stable
 Co-Chairs shall subsequently set a GitHub label indicating the result as
 either ``Stable'' (indicating that the proposed elements have
 been elevated to that class) or ``Pushed Back''. Accepted
-proposals can be committed to the next minor release version by the
+proposals can be committed to the next major release version by the
 Release Manager in accordance with their schedule.
 
 Proposals that are pushed back at any point can be modified and