From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2771 invoked from network); 10 May 2001 17:09:56 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 10 May 2001 17:09:56 -0000 Received: (qmail 13829 invoked by alias); 10 May 2001 17:09:51 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 14302 Received: (qmail 13805 invoked from network); 10 May 2001 17:09:50 -0000 From: "Bart Schaefer" Message-Id: <1010510170846.ZM19670@candle.brasslantern.com> Date: Thu, 10 May 2001 17:08:45 +0000 In-Reply-To: <20010510110356.76912.qmail@web10403.mail.yahoo.com> Comments: In reply to Felix Rosencrantz "Release process" (May 10, 4:03am) References: <20010510110356.76912.qmail@web10403.mail.yahoo.com> In-Reply-To: Comments: In reply to Peter Stephenson "Re: Release process" (May 10, 12:33pm) X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: Release process MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On May 10, 4:03am, Felix Rosencrantz wrote: } Subject: Release process } } Quiet time to me would be heavy restrictions on what can get checked } in. I'd suggest things like no C code changes, unless they fix a } crashing or other very serious bug. This would be another reason to use a CVS branch. Put the release code on the branch; let people continue committing whatever they happen to be working on, on the trunk; if it turns out to be a critical bug fix and does not destabilize anything, selectively merge it to the branch. On May 10, 12:33pm, Peter Stephenson wrote: } Subject: Re: Release process } } That's fine. It's been almost a year since the last full release anyway, } and goodness knows how long since the first 3.0. It'll be 5 years in August (June if you count pre-releases). -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net