incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject svn commit: r441987 - in /incubator/public/trunk: site-author/guides/releasemanagement.xml site-publish/guides/releasemanagement.html
Date Sun, 10 Sep 2006 19:10:35 GMT
Author: rdonkin
Date: Sun Sep 10 12:10:35 2006
New Revision: 441987

URL: http://svn.apache.org/viewvc?view=rev&rev=441987
Log:
Added comments on release management. Organisation of this document needs reworking.

Modified:
    incubator/public/trunk/site-author/guides/releasemanagement.xml
    incubator/public/trunk/site-publish/guides/releasemanagement.html

Modified: incubator/public/trunk/site-author/guides/releasemanagement.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-author/guides/releasemanagement.xml?view=diff&rev=441987&r1=441986&r2=441987
==============================================================================
--- incubator/public/trunk/site-author/guides/releasemanagement.xml (original)
+++ incubator/public/trunk/site-author/guides/releasemanagement.xml Sun Sep 10 12:10:35 2006
@@ -73,6 +73,38 @@
     </section>
     </section>
     <section id='guidelines'><title>Guidelines</title>
+    	<section id='process'><title>Release Process</title>
+    		<p>
+The minimal formal requirements for an official ASF release are (contrary to rumor) minimal.
+A successful binding VOTE by a project means that the artifact is an official ASF release.
+Release approved by project must comply with the current ASF release policies.
+Those with binding votes must check that the release complies with these policies.
+    		</p>
+    		<p>
+ In practice, most project adopt more ceremony than this minimum for a number of important
reasons. 
+ 			</p>
+ 			<p>
+ ASF releases are often widely distributed and long lived. Expect to be publically held to
account 
+ for a substandard release for a long time to come. 
+    		</p>
+			<p>
+As a project matures and its reputation grows, the consequences of a poor quality release
increase.
+It is therefore typical for mature projects to use release candidates, beta, alphas and so
on. 
+This ceremony is usually not necessary for neonate projects but may need to be adopted in
time.
+			</p>
+			<p>
+			TODO: release models - describe process models for more complex projects.
+			</p>
+    	</section>
+    	<section id='policies'><title>ASF Release Policy</title>
+    		<p>
+Policy is set by the board and by board committees (legal, infra, prc). 
+    		</p>
+    		<p>
+it is simple but subtle (it's rare for components to create complient releases first time).
+
+    		</p>
+    	</section>
         <p>
 It is strong recommended that a project creates it's own release guidelines. The actual 
 <a href='#rules'>minimum</a> required by the ASF is reasonable small but subtle.
However,
@@ -491,6 +523,12 @@
             <p>
             TODO (include link to infra documentation)
             </p>
+        </section>
+        <section id='glossary-ceremony'><title>Ceremony</title>
+        	<p>
+        	Process and procedure associated with - but not necessary to - a particular end.
+        	TODO: link to foundation docs
+        	</p>
         </section>
         <section id='glossary-manifest'><title>Jar MANIFEST</title>
         	<p>

Modified: incubator/public/trunk/site-publish/guides/releasemanagement.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/releasemanagement.html?view=diff&rev=441987&r1=441986&r2=441987
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasemanagement.html (original)
+++ incubator/public/trunk/site-publish/guides/releasemanagement.html Sun Sep 10 12:10:35
2006
@@ -152,6 +152,44 @@
    <a name="guidelines">Guidelines</a>
 </h2>
 <div class="section-content">
+<h3>
+   <a name="process">Release Process</a>
+</h3>
+<div class="section-content">
+<p>
+The minimal formal requirements for an official ASF release are (contrary to rumor) minimal.
+A successful binding VOTE by a project means that the artifact is an official ASF release.
+Release approved by project must comply with the current ASF release policies.
+Those with binding votes must check that the release complies with these policies.
+    		</p>
+<p>
+ In practice, most project adopt more ceremony than this minimum for a number of important
reasons. 
+ 			</p>
+<p>
+ ASF releases are often widely distributed and long lived. Expect to be publically held to
account 
+ for a substandard release for a long time to come. 
+    		</p>
+<p>
+As a project matures and its reputation grows, the consequences of a poor quality release
increase.
+It is therefore typical for mature projects to use release candidates, beta, alphas and so
on. 
+This ceremony is usually not necessary for neonate projects but may need to be adopted in
time.
+			</p>
+<p>
+			TODO: release models - describe process models for more complex projects.
+			</p>
+</div>
+<h3>
+   <a name="policies">ASF Release Policy</a>
+</h3>
+<div class="section-content">
+<p>
+Policy is set by the board and by board committees (legal, infra, prc). 
+    		</p>
+<p>
+it is simple but subtle (it's rare for components to create complient releases first time).
+
+    		</p>
+</div>
 <p>
 It is strong recommended that a project creates it's own release guidelines. The actual 
 <a href="#rules">minimum</a> required by the ASF is reasonable small but subtle.
However,
@@ -656,6 +694,15 @@
 <p>
             TODO (include link to infra documentation)
             </p>
+</div>
+<h3>
+   <a name="glossary-ceremony">Ceremony</a>
+</h3>
+<div class="section-content">
+<p>
+        	Process and procedure associated with - but not necessary to - a particular end.
+        	TODO: link to foundation docs
+        	</p>
 </div>
 <h3>
    <a name="glossary-manifest">Jar MANIFEST</a>



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message