Return-Path: Delivered-To: apmail-jakarta-avalon-dev-archive@jakarta.apache.org Received: (qmail 42326 invoked by uid 500); 23 Apr 2001 14:28:10 -0000 Mailing-List: contact avalon-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: "Avalon Development" Delivered-To: mailing list avalon-dev@jakarta.apache.org Received: (qmail 42261 invoked from network); 23 Apr 2001 14:28:08 -0000 Importance: Normal Subject: Re: Volunteer for Framework Release Manager To: "Avalon Development" X-Mailer: Lotus Notes Release 5.0.4 June 8, 2000 Message-ID: From: "Sam Ruby" Date: Mon, 23 Apr 2001 10:27:17 -0400 X-MIMETrack: Serialize by Router on D04NM301/04/M/IBM(Release 5.0.6 |December 14, 2000) at 04/23/2001 10:28:06 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Berin Loritsch wrote: > > I would like to volunteer for the role of Avalon Framework Release Manager. If I may be so bold, may I suggest that work begin on a release plan? An example that you can strip down or add to as necessary can be found at: http://jakarta.apache.org/cvsweb/index.cgi/~checkout~/jakarta-tomcat/RELEASE-PLAN-3.3?content-type=text/plain Such a release plan, once ready, would be put up for a vote. Contained in the release plan would be the name of the release manager. - Sam Ruby P.S. The release plan I am pointing to as an example contains dates. If you feel it is more appropriate, specify exit criteria instead. --------------------------------------------------------------------- To unsubscribe, e-mail: avalon-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: avalon-dev-help@jakarta.apache.org