Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 94360 invoked from network); 20 Jan 2004 18:48:20 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Jan 2004 18:48:20 -0000 Received: (qmail 10517 invoked by uid 500); 20 Jan 2004 18:47:46 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 10431 invoked by uid 500); 20 Jan 2004 18:47:45 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 10389 invoked from network); 20 Jan 2004 18:47:45 -0000 Received: from unknown (HELO mail.devtech.com) (66.112.202.2) by daedalus.apache.org with SMTP; 20 Jan 2004 18:47:45 -0000 Received: from localhost ([127.0.0.1]) by mail.devtech.com (JAMES SMTP Server 2.2.0-dev) with SMTP ID 5 for ; Tue, 20 Jan 2004 13:47:47 -0500 (EST) From: "Noel J. Bergman" To: "Jakarta Commons Developers List" Subject: RE: [net][vote]Steve Cohen to manage release of v1.2.0 of commons.net Date: Tue, 20 Jan 2004 13:47:45 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <200401201002.08559.scohen@javactivity.org> Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N > 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