cziegeler 2004/07/09 03:22:51
Modified: src/documentation/content/xdocs/devinfo releasing.xml
Log:
New voting rule for the release
Revision Changes Path
1.6 +19 -2
cocoon-site/src/documentation/content/xdocs/devinfo/releasing.xml
Index: releasing.xml
===================================================================
RCS file:
/home/cvs/cocoon-site/src/documentation/content/xdocs/devinfo/releasing.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- releasing.xml 9 Jul 2004 09:06:29 -0000 1.5
+++ releasing.xml 9 Jul 2004 10:22:51 -0000 1.6
@@ -43,13 +43,14 @@
<section>
<title>The Release Process</title>
<p>
- This is a step-by-step procedure.
+ This is a step-by-step procedure that covers the last eight days
before
+ the actual release date.
</p>
<section>
<title>Code Freeze</title>
<p>
Prior to the release day, a code freeze should be announced
approx.
- seven days in advance.
+ eight days in advance.
</p>
</section>
<section>
@@ -59,6 +60,22 @@
test distribution, find and fix bugs and update the documentation.
if
desired an invitation to the community to help in polishing the
release
can be send out to the mailing lists.
+ </p>
+ </section>
+ <section>
+ <title>Voting the release tarball</title>
+ <p>
+ Three days before the actual release date, a release tarball is
generated
+ and put on a publically reachable location. Now a vote is started
for the
+ next 72h if this tarball can be used as the final release. This
tarball
+ only differs in the version information.
+ </p>
+ <p>
+ During this period, no commits should alter the repository.
+ </p>
+ <p>
+ If the vote is accepted, the release process is started. If the
vote fails,
+ it has to be decided what to do next.
</p>
</section>
<section>
