[zeta-commits] svn commit: r1043082 - /incubator/zetacomponents/docs/release_process.txt

[to...@apache.org]

Author: toby
Date: Tue Dec  7 15:07:05 2010
New Revision: 1043082

URL: http://svn.apache.org/viewvc?rev=1043082&view=rev
Log:
- Updated: Incorporated comments from the mailinglist.

Modified:
    incubator/zetacomponents/docs/release_process.txt

Modified: incubator/zetacomponents/docs/release_process.txt
URL: http://svn.apache.org/viewvc/incubator/zetacomponents/docs/release_process.txt?rev=1043082&r1=1043081&r2=1043082&view=diff
==============================================================================
--- incubator/zetacomponents/docs/release_process.txt (original)
+++ incubator/zetacomponents/docs/release_process.txt Tue Dec  7 15:07:05 2010
@@ -118,13 +118,16 @@ __ http://people.apache.org/
 .. note:: Incubating phase
 
    After a successful vote on the developer mailinglist, the release manager
-   must open another vote on the Incubator PMC mailinglist for the release.
+   must cast another vote on the Incubator PMC mailinglist for the release.
    This vote must contain:
 
    - A reference to the RC package
    - A reference to the successful developer vote
    - A reference to the SVN tag for the release
 
+   This process is dropped, once Zeta Components graduated to a top-level
+   Apache project.
+
 When the vote is accepted, the release manager is in charge of uploading the
 release to the Apache dist server and to announce the release.
 
@@ -150,18 +153,15 @@ requires the process specified above:
 Full package release
 ====================
 
-A full package release does not occur as needed, but fixed dates twice a year.
+A full package release does not occur as needed, but fixed dates twice a year:
 
-.. note:: Determine release times.
+- Before the summer vacation time (around July)
+- Before X-mas (early December)
 
-The release manager for this release is elected on the developer list through a
-vote, right after the last release has been rolled. The full package release
-does not require *alpha* and *beta* stages, since it only contains the most
-recent stable releases of all components.
-
-In order to roll a release, the release manager must start casting the votes
-for it in the same manor as described for `Component releases`_ 2 weeks before
-the release should be published.
+A release manager for the next release is elected on the developer list through
+a vote, right after the last release has been rolled. He is responsible for
+tracking the release, casting the necessary votes and for packaging and
+distributing it.
 
 
 ..