incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject svn commit: r806025 - in /incubator/public/trunk: site-author/guides/releasemanagement.xml site-publish/guides/releasemanagement.html
Date Thu, 20 Aug 2009 02:57:06 GMT
Author: joes
Date: Thu Aug 20 02:57:06 2009
New Revision: 806025

URL: http://svn.apache.org/viewvc?rev=806025&view=rev
Log:
process docs for the RM

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?rev=806025&r1=806024&r2=806025&view=diff
==============================================================================
--- incubator/public/trunk/site-author/guides/releasemanagement.xml [utf-8] (original)
+++ incubator/public/trunk/site-author/guides/releasemanagement.xml [utf-8] Thu Aug 20 02:57:06
2009
@@ -2056,8 +2056,44 @@
         </section>
         <section id='glossary-release-manager'><title>Release Manager</title>
         	<p>
-Committer responsible for shepherding the release. 
+Committer responsible for shepherding the release.  This role is rather time consuming
+and often involves tedious tasks, but it is essential that the release manager keep
+on top of everything.  Release managers may be elected for a release by the project
+by formal vote, or by invoking lazy consensus, but such votes are not really necessary.
         	</p>
+                <p>
+Once a release manager has stepped forward, the first thing they should do is to
+consult and correct the project's release documentation.  Once that has been addressed,
+the candidate artifacts should be prepared and a formal vote on those artifacts must be
+conducted by the release manager on the project's development list.  All votes are
+welcome, but only those votes by the project's PPMC members (or IPMC members) count
+towards the final tally.  The voting period should be no less than 72 hours, and at
+the end of the voting the release manager should post a final tally to the list.
+                </p>
+                <p>
+The vote passes if there are at least 3 +1's from the PPMC/IPMC members and more
++1's than -1's.  This is what is meant by majority consensus.  If you've gotten
+this far, congratulations, you're nearly ready to upload and announce the release.
+                </p>
+                <p>
+It is Apache policy that all releases be formally approved by the responsible PMC.
+In the case of the incubator, the IPMC must approve all releases.  That means there
+is an additional bit of voting that the release manager must now oversee on
+general@incubator in order to gain that approval.  The release manager must inform
+general@incubator that the vote has passed on the project's development list, and
+should indicate any IPMC votes gained during that process.  A new vote on the
+release candidate artifacts must now be held on general@incubator to seek majority
+consensus from the IPMC.  Previous IPMC votes issued on the project's development
+list count towards that goal.
+                </p>
+                <p>
+Once the 72-hour minimum voting period has ended on general@incubator, the release
+manager should tally the votes and declare a result.  If majority consensus has
+been achieved with respect to IPMC votes, the release manager may proceed with the
+release.  Read the remainder of this document for details on the remaining steps
+regarding uploading artifacts to the podling's distribution directory, dealing with
+maven central if appropriate, and announcing the release to the public.
+                </p>
             <p>
             TODO (include link to infra documentation)
             TODO say something about the technical release manager (who

Modified: incubator/public/trunk/site-publish/guides/releasemanagement.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/releasemanagement.html?rev=806025&r1=806024&r2=806025&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasemanagement.html [utf-8] (original)
+++ incubator/public/trunk/site-publish/guides/releasemanagement.html [utf-8] Thu Aug 20 02:57:06
2009
@@ -2943,9 +2943,45 @@
 </h3>
 <div class="section-content">
 <p>
-Committer responsible for shepherding the release. 
+Committer responsible for shepherding the release.  This role is rather time consuming
+and often involves tedious tasks, but it is essential that the release manager keep
+on top of everything.  Release managers may be elected for a release by the project
+by formal vote, or by invoking lazy consensus, but such votes are not really necessary.
         	</p>
 <p>
+Once a release manager has stepped forward, the first thing they should do is to
+consult and correct the project's release documentation.  Once that has been addressed,
+the candidate artifacts should be prepared and a formal vote on those artifacts must be
+conducted by the release manager on the project's development list.  All votes are
+welcome, but only those votes by the project's PPMC members (or IPMC members) count
+towards the final tally.  The voting period should be no less than 72 hours, and at
+the end of the voting the release manager should post a final tally to the list.
+                </p>
+<p>
+The vote passes if there are at least 3 +1's from the PPMC/IPMC members and more
++1's than -1's.  This is what is meant by majority consensus.  If you've gotten
+this far, congratulations, you're nearly ready to upload and announce the release.
+                </p>
+<p>
+It is Apache policy that all releases be formally approved by the responsible PMC.
+In the case of the incubator, the IPMC must approve all releases.  That means there
+is an additional bit of voting that the release manager must now oversee on
+general@incubator in order to gain that approval.  The release manager must inform
+general@incubator that the vote has passed on the project's development list, and
+should indicate any IPMC votes gained during that process.  A new vote on the
+release candidate artifacts must now be held on general@incubator to seek majority
+consensus from the IPMC.  Previous IPMC votes issued on the project's development
+list count towards that goal.
+                </p>
+<p>
+Once the 72-hour minimum voting period has ended on general@incubator, the release
+manager should tally the votes and declare a result.  If majority consensus has
+been achieved with respect to IPMC votes, the release manager may proceed with the
+release.  Read the remainder of this document for details on the remaining steps
+regarding uploading artifacts to the podling's distribution directory, dealing with
+maven central if appropriate, and announcing the release to the public.
+                </p>
+<p>
             TODO (include link to infra documentation)
             TODO say something about the technical release manager (who
             cuts the release) and the social one (who organizes it).



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


Mime
View raw message