commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <n...@devtech.com>
Subject RE: [net][vote]Steve Cohen to manage release of v1.2.0 of commons.net
Date Tue, 20 Jan 2004 18:47:45 GMT
> http://jakarta.apache.org/commons/releases/prepare.html

Missed that when I went looking.  The assumptions made by that document
differ a bit from what is stated by
http://jakarta.apache.org/site/decisions.html.  Since the text comes almost
verbatim from http://httpd.apache.org/dev/guidelines.html, I would hope that
the detailed description under http://httpd.apache.org/dev/release.html also
apply, with changes in nomenclature and technical process as documented by
http://jakarta.apache.org/commons/releases/.

The guidelines documents all state: "A release plan is used to keep all
volunteers aware of when a release is desired, who will be the release
manager, when the repository will be frozen to create a release, and other
assorted information to keep volunteers from tripping over each other. Lazy
majority decides each issue in a release plan."  However, the detailed
procedure makes it clear that the CVS is never frozen.  Tags and/or branches
are used to handle the process.  This becomes much easier with Subversion.

AIUI, a release plan is about coordination, and to communicate what is going
into the release.  For example, will you (as the release manager) be picking
up the recent NNTP patches?  Will this release continue to be compatible
with the same JDK levels as the previous release?  Etc.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message