From dev-return-13566-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org Tue Jul 05 02:25:20 2005 Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 67338 invoked from network); 5 Jul 2005 02:25:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 5 Jul 2005 02:25:19 -0000 Received: (qmail 55520 invoked by uid 500); 5 Jul 2005 02:25:15 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 55488 invoked by uid 500); 5 Jul 2005 02:25:14 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 55474 invoked by uid 99); 5 Jul 2005 02:25:14 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jul 2005 19:25:14 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [66.250.40.202] (HELO saturn.opentools.org) (66.250.40.202) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jul 2005 19:25:15 -0700 Received: by saturn.opentools.org (Postfix, from userid 500) id 9E8073F63; Mon, 4 Jul 2005 22:26:40 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by saturn.opentools.org (Postfix) with ESMTP id 96C81F349 for ; Mon, 4 Jul 2005 22:26:40 -0400 (EDT) Date: Mon, 4 Jul 2005 22:26:40 -0400 (EDT) From: Aaron Mulder X-X-Sender: ammulder@saturn.opentools.org To: dev@geronimo.apache.org Subject: Re: Preparation for M4 In-Reply-To: <20050705021534.GA18755@django> Message-ID: References: <20050704212155.GD18287@django> <42C9D2CC.80306@apache.org> <20050705012722.GA18701@django> <42C9E48F.30803@apache.org> <20050705021534.GA18755@django> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I guess we should also decide whether to make Jetty or Tomcat the default container, and whether to provide separate builds for each. Also, we need to decide whether we're planning to run the entire TCK on the candidate configuration(s). Aaron On Mon, 4 Jul 2005, David Blevins wrote: > On Mon, Jul 04, 2005 at 06:38:23PM -0700, Jeremy Boynes wrote: > > David Blevins wrote: > > >On Mon, Jul 04, 2005 at 05:22:36PM -0700, Jeremy Boynes wrote: > > > > > >>David Blevins wrote: > > >> > > >>>Anything I missed? > > >>> > > >> > > >>SNAPSHOT elimination so the build is reproducible. > > > > > > > > >Right. Missed that one for M3 IIRC. > > > > > > > > >>Branch so that M4 can stabilize whilst other changes are being made. > > > > > > > > >We do for every milestone. Don't expect this to be different. > > > > > > > > >>Acceptance test process - how do we know what works (need to avoid a > > >>broken release like M3). > > > > > > > > >That's what I meant by: > > > > > > DB> We have a number of people interested in testing. I'll ping > > > DB> them when I have something ready. > > > > > >Was thinking to branch when I dish out the binaries for testing. > > >Rather than the "surprise, here is a binary" approach we've done in > > >the past. Sounds pretty much like what you are proposing as well. > > > > > > > Yes - in the past we've just tagged and moved on. This time I think we > > should create the branch at the start of the process rather than at the > > end as there seem to be a lot of pent up changes planned. Yes, we may > > need to merge some critical changes back to this branch but hopefully > > this can be kept to a minimum. > > > > So basically, > > * create a branch now, say 1.0-M4-prep > > * do the stuff we talking about now on that branch > > * cut the final M4 distro > > * drop the 1.0-M4-prep branch > > > > Other work can continue on the trunk without destablizing the M4 release. > > > > +1 That's pretty much what I had in mind. > > > -David >