Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 23693 invoked from network); 22 Aug 2007 05:45:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Aug 2007 05:45:23 -0000 Received: (qmail 7337 invoked by uid 500); 22 Aug 2007 05:45:15 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 7297 invoked by uid 500); 22 Aug 2007 05:45:15 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 7286 invoked by uid 99); 22 Aug 2007 05:45:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2007 22:45:15 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [204.127.225.95] (HELO alnrmhc15.comcast.net) (204.127.225.95) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2007 05:45:13 +0000 Received: from [192.168.0.100] (c-68-33-79-168.hsd1.md.comcast.net[68.33.79.168]) by comcast.net (alnrmhc15) with ESMTP id <20070822054452b1500a1sqte>; Wed, 22 Aug 2007 05:44:52 +0000 Message-ID: <46CBCD53.7080500@apache.org> Date: Wed, 22 Aug 2007 01:44:51 -0400 From: Mark Thomas User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Tomcat Developers List Subject: Re: [VOTE] Send trunk to the sandbox References: <20070813181349.791471A981A@eris.apache.org> <46CA1D3B.1070204@apache.org> In-Reply-To: <46CA1D3B.1070204@apache.org> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Mark Thomas wrote: > Bill Barker wrote: >> I'm so tired of this thread, so let's settle it once and for all. I'm >> backing Remy's suggestion to send the current trunk to the sandbox: >> [X] +1 Let's end the revolution >> [ ] +0 What revolution? >> [ ] -1 Viva the revolultion > > This applies to this proposal only. Other changes should be proposed > in other threads. Expanding on what I said on private@ as I see no reason for it not to be part of the public discussion... I don't see a need for a separate 6.0.x and 6.1.x development at this point. I have yet to see a convincing technical argument that there is something sufficiently new and/or different to justify this overhead. There is enough work to do to maintain 4.1.x, 5.0.x (which we aren't doing a great job of and I am several months past my promise to do a security release for 5.0.x), 5.5.x and 6.0.x without adding yet an other branch. Simply, trunk should never have been called trunk, it is a branch. It should be moved to 6.0.x/branches/whatever In terms of moving forward, merge the changes in 'trunk' to 6.0.x. Ideally this should be done commit by commit or groups of related commits so we can discuss each of the additions if necessary. If any attract a veto or are viewed as too experimental etc they can stay in 6.0.x/branches/whatever until the issues are resolved or that feature is abandoned. My expectation is that 99% of what is in /trunk can move to 6.0.x/trunk with little or no debate. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org