Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 32198 invoked from network); 2 Feb 2001 18:27:20 -0000 Received: from nautilus.shore.net (207.244.124.104) by h31.sny.collab.net with SMTP; 2 Feb 2001 18:27:20 -0000 Received: from netbstn-s04-59.port.shore.net (shore.net) [204.167.108.59] by nautilus.shore.net with esmtp (Exim) for tomcat-dev@jakarta.apache.org id 14Okva-00064c-00; Fri, 02 Feb 2001 13:27:23 -0500 Sender: danmil Message-ID: <3A7AFB46.994E8F06@shore.net> Date: Fri, 02 Feb 2001 13:24:06 -0500 From: Dan Milstein X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i686) X-Accept-Language: en MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: 3.2.2 Release? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Can someone who has functioned as a release manager for a dot release give me a quick overview of what's involved? I may be able to find the time, but I'm not totally clear on the scope of what needs to happen. I don't think Milestone releases would make sense -- from what it says on http://jakarta.apache.org/site/binindex.html, those sound like they should really be steps towards a major release of new functionality, not snapshots of bug fixes in a released product. Nightly builds I would be fine with, however. -Dan cmanolache@yahoo.com wrote: > > > I'm in the same boat right now. I'd love to a 3.2.2 released but I'm way > > too busy right now to manage a release. > > What about a "milestone" ? It doesn't have all the requirements of a > release. I can add a nightly build of 3.2.x to my scripts too ? ( it'll > not be a "blessed" release, but people who need the patches can use it ). > > Costin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org > For additional commands, email: tomcat-dev-help@jakarta.apache.org -- Dan Milstein // danmil@shore.net