Merge pull request #7 from kathrynmohror/master

Adding Guidance Section to Governance Document

Author: jjhursey

pmix_governance.tex

@@ -158,7 +158,7 @@ \subsubsection{ASC Duties and Organization }
 time of the two-year service period of the original Co-Chair. The
 replacement Co-Chair may seek election in subsequent terms.
 
-\subsubsection{ASC Participation}
+\subsubsection{ASC Participation}\label{gov-asc-participation}
 Participation in the consortium is both formal and informal:
 
 \begin{itemize}
@@ -425,6 +425,31 @@ \subsubsection{ASC Secretaries}\label{asc-secretaries}}
 Alternate for a Member may vote on behalf of the Member subject to the
 one vote per Member limit.
 
+\hypertarget{asc-guidance}{%
+\subsection{ASC Guidance}\label{asc-guidance}}
+
+This section provides general guidance for the PMIx ASC and participants.
+The rationale behind providing this guidance is to outline
+philosophy and best practices the ASC should follow in 
+maintaining the PMIx Standard. 
+
+\hypertarget{release-schedule-guidance}{%
+\subsubsection{Release Schedule Guidance}\label{release-schedule-guidance}}
+
+As described in Section~\ref{release-managers},
+the schedule of major releases of the PMIx
+Standard is determined by the Release Managers in coordination with other
+members of the ASC. There is no prescribed major release schedule that the
+Release Managers must follow. However, the Release Managers will prioritize
+timely releases of substantive changes to the Stable entries in the 
+PMIx Standard. Substantive changes
+include: deprecated or removed
+APIs, keys, or other text in the standard; alterations of APIs or keys; and
+alterations of text that result in changed meaning or clarifications. The
+Release Managers will prioritize major releases of the standard over waiting for
+additional changes that are in progress but not yet accepted by the ASC.
+
+
 \hypertarget{the-standardization-process}{%
 \subsection{The Standardization
 Process}\label{the-standardization-process}}