Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 40929 invoked from network); 20 Sep 2005 04:51:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 20 Sep 2005 04:51:02 -0000 Received: (qmail 55656 invoked by uid 500); 20 Sep 2005 04:51:00 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 54964 invoked by uid 500); 20 Sep 2005 04:50:58 -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 54951 invoked by uid 99); 20 Sep 2005 04:50:58 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Sep 2005 21:50:58 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received: from [208.42.156.2] (HELO conn.mc.mpls.visi.com) (208.42.156.2) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 Sep 2005 21:51:06 -0700 Received: from [192.168.42.12] (68-171-59-126.vnnyca.adelphia.net [68.171.59.126]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by conn.mc.mpls.visi.com (Postfix) with ESMTP id 43DE082FC for ; Mon, 19 Sep 2005 23:50:43 -0500 (CDT) Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <74e15baa050919210238db510b@mail.gmail.com> References: <604FADE8-DA00-46F9-9078-DDBECA0832BD@apache.org> <432F544E.3040802@apache.org> <22CB655C-9B6E-432C-AC27-C4F285C1472F@iq80.com> <74e15baa0509191746127fabad@mail.gmail.com> <432F6887.4040204@hogstrom.org> <432F73A4.5010204@savoirtech.com> <432F843D.7040308@apache.org> <432F87C1.5060602@savoirtech.com> <74e15baa050919210238db510b@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0325796E-1523-4551-9C74-6D3473CC940F@visi.com> Content-Transfer-Encoding: quoted-printable From: David Blevins Subject: Re: [discuss] branch and tag policy (and stable/unstable mixed in :) - refocus Date: Mon, 19 Sep 2005 21:50:31 -0700 To: dev@geronimo.apache.org X-Mailer: Apple Mail (2.734) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Alright guys, we're talking over each other again and are too far =20 down in the details. This entire thing started as Geir wanted to do 1.0-M5.1, 1.0-M5.2, =20 1.0-M5.3, ... 1.0-M5.N while we all work on 1.0-M6 (or whatever). That's not a bad goal, but we have to agree on what we are going for =20 before we can decide what to call it. So... Are we going to put a stake in the sand now and start doing minor =20 revisions (patch only, no new features) on this release... or are we =20 going to wait till some time in the future=10? I am totally cool with whatever, but we have to get on the same page =20 first. If we decide to put a stake in the sand now and branch off a =20 stabilization effort, we will need to define at least at a high level =20= what "stable" means to us in terms of the actual code, functionality, =20= and files that comprise our software. There must be some common =20 yardstick on which we measure stable/unstable. -David=