[prev in list] [next in list] [prev in thread] [next in thread]
List: forrest-svn
Subject: svn commit: r549338 - in /forrest/trunk/site-author/content/xdocs:
From: crossley () apache ! org
Date: 2007-06-21 3:04:40
Message-ID: 20070621030441.01E9C1A981A () eris ! apache ! org
[Download RAW message or body]
Author: crossley
Date: Wed Jun 20 20:04:39 2007
New Revision: 549338
URL: http://svn.apache.org/viewvc?view=rev&rev=549338
Log:
Remind people about our voting guidelines and actions, and about Release Manager \
decisions.
Modified:
forrest/trunk/site-author/content/xdocs/guidelines.xml
forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
forrest/trunk/site-author/content/xdocs/site.xml
Modified: forrest/trunk/site-author/content/xdocs/guidelines.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/guidelines.xml?view=diff&rev=549338&r1=549337&r2=549338
==============================================================================
--- forrest/trunk/site-author/content/xdocs/guidelines.xml (original)
+++ forrest/trunk/site-author/content/xdocs/guidelines.xml Wed Jun 20 20:04:39 2007
@@ -443,6 +443,7 @@
</td>
<td>
Defines the timetable and actions for a release.
+ A release plan cannot be vetoed (hence lazy majority).
</td>
<td>
Lazy majority
@@ -458,6 +459,10 @@
When a release of one of the project's products is ready, a vote is
required to accept the release as an official release of the
project.
+ A release cannot be vetoed (hence lazy majority).
+ The <link href="site:howToRelease/ReleaseManager">Release Manager</link>
+ might choose to get an issue resolved or re-schedule, but that is
+ their <link href="site:howToRelease/decisionRM">decision</link>.
</td>
<td>
Lazy majority
Modified: forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml?view=diff&rev=549338&r1=549337&r2=549338
==============================================================================
--- forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml \
(original)
+++ forrest/trunk/site-author/content/xdocs/procedures/release/How_to_release.xml Wed \
Jun 20 20:04:39 2007 @@ -115,10 +115,10 @@
<p>
The project developers have the role of preparing the product to release
quality, testing, fixing issues, and voting for the release candidate.
- The votes of the PMC will decide whether the product is fit for release.
+ The votes of the PMC will <a href="#vote">decide</a> whether the product is \
fit for release. </p>
<p>
- The RM makes all the decisions regarding the actual preparations and the
+ The RM makes all the <a href="#decisionRM">decisions</a> regarding the \
actual preparations and the
doing of the release. Many projects have the same release manager for
years.
</p>
@@ -194,6 +194,10 @@
encouraging a strong
<a href="http://www.apache.org/dev/release-signing.html#web-of-trust">web \
of trust</a>. </li>
+ <li>
+ Be familiar with our <a href="site:guidelines/voting">voting \
guidelines</a> and + <a href="site:guidelines/actions">release actions</a>.
+ </li>
</ul>
<fixme author="open">
Decide the content of the release. Previously we just packed everything
@@ -258,7 +262,7 @@
Releases</a> and our download notes for the
<a href="http://forrest.apache.org/mirrors.cgi#verify">Verification</a>.
</p></li>
- <li>Practice signing email in readiness for the announcment.</li>
+ <li>Practice signing email in readiness for the announcement.</li>
<li>Investigate the release procedure notes of other ASF projects.</li>
<li>
Make sure that the network connection is reliable and efficient.
@@ -299,6 +303,10 @@
and propose your plan, then call for a quick vote on the release plan on
the dev list.
</p>
+ <p>
+ Remind people about our <a href="site:guidelines/voting">voting \
guidelines</a> and + <a href="site:guidelines/actions">release actions</a>.
+ </p>
<note>
There are various reasons for voting on the Release Plan, e.g. makes
people aware that a code-freeze is about to happen; encourage them to
@@ -765,7 +773,8 @@
<li>Encourage people to build some difficult sites.</li>
<li>Remind people about how long remains for testing.</li>
</ul></li>
- <li>If substantial problems are revealed (not just minor glitches) then \
co-ordinate their + <li id="decisionRM">
+ If substantial problems are revealed (not just minor glitches) then \
co-ordinate their
fixing by other developers. Doing the fixing of issues is not the \
Release Manager's job.
Deciding what constitutes a "substantial" issue is entirely the \
RM's call.
Remember that there is still a code freeze, so don't let people be \
tempted to fix other
Modified: forrest/trunk/site-author/content/xdocs/site.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/site.xml?view=diff&rev=549338&r1=549337&r2=549338
==============================================================================
--- forrest/trunk/site-author/content/xdocs/site.xml (original)
+++ forrest/trunk/site-author/content/xdocs/site.xml Wed Jun 20 20:04:39 2007
@@ -58,6 +58,8 @@
<guidelines label="Project guidelines" href="guidelines.html"
description="Open development guidelines to encourage participation">
<way href="#way"/>
+ <voting href="#voting"/>
+ <actions href="#actions"/>
</guidelines>
<committed label="Being committed" href="committed.html" description="Notes \
about contribution"/>
<roles label="Project roles" href="roles.html" description="Tasks to keep the \
project flowing"/> @@ -108,7 +110,10 @@
<zoneMangement label="Zone management" href="zone.html"
description="Notes for committers to manage forrest.zones.apache.org"/>
<howToRelease label="How to release" \
href="procedures/release/How_to_release.html"
- description="Instructions on preparing and creating a new Forrest \
release."/> + description="Instructions on preparing and creating a new \
Forrest release."> + <ReleaseManager href="#rm"/>
+ <decisionRM href="#decisionRM"/>
+ </howToRelease>
<howToPublishDocs label="Publishing Forrest documentation" \
href="procedures/How_to_publish_docs.html" description="Instructions on publishing \
the Forrest Website"/>
</committers>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic