Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 39011 invoked by uid 500); 5 Feb 2001 04:14:42 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 38987 invoked from network); 5 Feb 2001 04:14:40 -0000 X-Authentication-Warning: kurgan.lyra.org: gstein set sender to gstein@lyra.org using -f Date: Sun, 4 Feb 2001 20:16:16 -0800 From: Greg Stein To: new-httpd@apache.org Subject: Re: Release Strategy Message-ID: <20010204201616.J26044@lyra.org> Mail-Followup-To: new-httpd@apache.org References: <20010205015453.7974.qmail@web3205.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from rbb@covalent.net on Sun, Feb 04, 2001 at 07:10:25PM -0800 X-URL: http://www.lyra.org/greg/ X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Sun, Feb 04, 2001 at 07:10:25PM -0800, rbb@covalent.net wrote: > > > > We may be best server by just having somebody run a cron job every > > > week. Thoughts about that? > > > > I think that's a very good idea. You might even have the cron job roll a tarball with > > the date stamp. But at least have the tagging be done automatically. =-) > > The reason I didn't want the roll to be done automatically is because we > are trying to separate the tag from the roll. As I understood Roy (and agree with this): we tag and roll continually. There is no separation of that step. The characterization of the release is what changes. Every tag/roll spits out a tarball to work with. If it is reasonably stable, then we call it an alpha. If it is good stuff, we call it a beta. etc. Calling it alpha, beta, whatever, comes after the tag/roll/test/whatever process. Cheers, -gx -- Greg Stein, http://www.lyra.org/