incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1550056 - /incubator/public/trunk/content/guides/release.xml
Date Wed, 11 Dec 2013 05:50:39 GMT
Author: marvin
Date: Wed Dec 11 05:50:39 2013
New Revision: 1550056

Flesh out the Release Procedure (formerly Manifest Usage).


Modified: incubator/public/trunk/content/guides/release.xml
--- incubator/public/trunk/content/guides/release.xml [utf-8] (original)
+++ incubator/public/trunk/content/guides/release.xml [utf-8] Wed Dec 11 05:50:39 2013
@@ -23,47 +23,52 @@ limitations under the License.
     <title>Experimental Release Guide (DRAFT)</title>
-    <section id='status'><title>DRAFT STATUS</title>
+    <section id='status'><title>DRAFT, EXPERIMENTAL STATUS</title>
       <p style="color:red">
 <strong>This document is part of a proposal currently being refined and is
 not yet ready for use.</strong>
+      <p>
+This document describes an experiment in which only selected podlings may take part.  The
procedure for joining the
+experiment is (will be) described in the <a
policy</a> page.
+      </p>
     <section id='intro'><title>Experimental Release Guide (DRAFT)</title>
           <section id='TOC'><title>Contents</title><toc/></section>
-    <section id='release-manifest-template'><title>Release Manifest Template</title>
+    <section id="manifest-usage"><title>Release Procedure</title>
+      <p>
+Once a release candidate is ready, the <a
+href="">Release Manager</a>
should create a <a
+Manifest</a> at$PODLING
and fill in all initial fields.
+      </p>
-The release manifest template is available <a
+A [VOTE] thread should be started on the podling's dev list in accordance with <a
policy on releases</a>.  The
+email kicking off the [VOTE] should contain a link URL for the Manifest.  While the [VOTE]
is in progress, reviewers
+update the Manifest accordingly.  Should the dev list [VOTE] pass, a [VOTE] on general@incubator
should be called, again
+in accordance with Incubator release <a
and again referencing the
+Manifest URL.
+      </p>
+      <p>
+Once the voting process concludes -- regardless of success or failure -- the Release Manager
should archive the Manifest
+permanently by moving it from votes/$PODLING/ to votes/$PODLING/archive/.
-    <section id="manifest-usage"><title>Release Manifest Usage</title>
-      <ol>
-        <li>
-Once a release is ready, create such a manifest at
-        </li>
-        <li>
-Drive the vote on the podling's dev list, reviewers update the manifest
-        </li>
-        <li>
-Bring the vote to general@incubator.a.o, pointing to the existing manifest.
-        </li>
-        <li>
-For both votes, +1s in the manifest are added to the [VOTE] thread votes.
-        </li>
-        <li>
-A given (to be defined) number of documented reviews in the manifest is
-required for the release to be approved.
-        </li>
-        <li>
-Release manifests are kept forever in svn, moved to an "archive" subfolder of
-$PODLING to make their status clear. 
-        </li>
-      </ol>
+    <section id='release-manifest-template'><title>Release Manifest Template</title>
+      <p>
+Podlings may start from the Incubator's <a href="release_manifest.txt">default
+Release Manifest</a> template or may customize a template to meet their own
+needs.  A list of suggested additional review items is maintained on the <a
+wiki page.
+      </p>
     <section id='review-items'><title>Review Item Explanations</title>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message