incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r828783 - in /websites/staging/incubator/trunk/content: ./ guides/releasemanagement.html report-next-month.html
Date Mon, 13 Aug 2012 09:30:51 GMT
Author: buildbot
Date: Mon Aug 13 09:30:51 2012
New Revision: 828783

Staging update by buildbot for incubator

    websites/staging/incubator/trunk/content/   (props changed)

Propchange: websites/staging/incubator/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Mon Aug 13 09:30:51 2012
@@ -1 +1 @@

Modified: websites/staging/incubator/trunk/content/guides/releasemanagement.html
--- websites/staging/incubator/trunk/content/guides/releasemanagement.html (original)
+++ websites/staging/incubator/trunk/content/guides/releasemanagement.html Mon Aug 13 09:30:51
@@ -2558,26 +2558,27 @@ Once a release manager has stepped forwa
 consult and correct the project's <a href="#glossary-release-documentation">release
 documentation</a>.  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
+on the project's development list.  [Note: this must be followed by a vote on the
+general@incubator list - see below.] All votes are welcome, but only those votes by the
 project's <a href="#glossary-ppmc">PPMC</a> members (or <a href="#glossary-ipmc">IPMC</a>
 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
-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.
+The PPMC 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.
 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
+general@incubator that the vote has passed on the podling'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.
+list count towards that goal. Even if there are sufficient IPMC votes already, it is
+vital that the IPMC as whole is informed via a VOTE e-mail on general@incubator.
 Once the 72-hour minimum voting period has ended on general@incubator, the release

Modified: websites/staging/incubator/trunk/content/report-next-month.html
--- websites/staging/incubator/trunk/content/report-next-month.html (original)
+++ websites/staging/incubator/trunk/content/report-next-month.html Mon Aug 13 09:30:51 2012
@@ -67,7 +67,7 @@
 <a href="">Apache Incubator</a> Podlings needing to
prepare report for September</h1>
 <div style="text-align:right;">
-<i>Generated on 2012-08-13T02:10:07Z</i>
+<i>Generated on 2012-08-13T09:30:57Z</i>

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

View raw message