Return-Path: Delivered-To: apmail-jakarta-oro-dev-archive@apache.org Received: (qmail 84085 invoked from network); 20 Aug 2003 00:42:41 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 20 Aug 2003 00:42:41 -0000 Received: (qmail 16694 invoked by uid 97); 20 Aug 2003 00:45:30 -0000 Delivered-To: qmlist-jakarta-archive-oro-dev@nagoya.betaversion.org Received: (qmail 16687 invoked from network); 20 Aug 2003 00:45:30 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 20 Aug 2003 00:45:30 -0000 Received: (qmail 82890 invoked by uid 500); 20 Aug 2003 00:42:13 -0000 Mailing-List: contact oro-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "ORO Developers List" Reply-To: "ORO Developers List" Delivered-To: mailing list oro-dev@jakarta.apache.org Received: (qmail 82786 invoked from network); 20 Aug 2003 00:42:10 -0000 Received: from umbongo.flamefew.net (64.253.103.114) by daedalus.apache.org with SMTP; 20 Aug 2003 00:42:09 -0000 Received: by umbongo.flamefew.net (Postfix on Linux (i386), from userid 500) id BDC8CC87; Tue, 19 Aug 2003 20:14:21 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by umbongo.flamefew.net (Postfix on Linux (i386)) with ESMTP id BCC19BB6; Tue, 19 Aug 2003 20:14:21 -0400 (EDT) Date: Tue, 19 Aug 2003 20:14:21 -0400 (EDT) From: Henri Yandell X-X-Sender: hen@umbongo.flamefew.net To: Jakarta Project Management Committee List Cc: oro-dev@jakarta.apache.org Subject: Re: jakarta-oro next steps In-Reply-To: <200308191824.h7JIOjQF023179@gandalf.savarese.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Tue, 19 Aug 2003, Daniel F. Savarese wrote: > > Henri wrote: > >I wrote: > >> I guess I'm looking for some confirmation of or pointer to the proper > >> ASF-compliant release procedure. > > > >Probably makes sense to follow the Commons release policies: > > Actually, what I meant to write was "proper ASF-compliant release approval > procedure" since the Jakarta convention has been to have committers vote > while Greg pointed out that it's the PMC's responsibility. In practice > if all committers are on the PMC, it works out. In any case, I just don't > recall ever reading anywhere how the PMC is supposed to oversee a release. > Everything I've ever read, including the HTTPD project release guidelines > (http://httpd.apache.org/dev/release.html) only talk about committers > voting. As far as I know, the current interpretation of the procedure [meaning the one in my head :)] is that the project votes on a release, then notifies the PMC of such a release, allowing the PMC time to veto the release. I think this feels pretty good. The people who are doing the day to day coding decide that they are ready for a release to be made. They then confirm with the people responsible for the project legally [the PMC] that a release may be made. I like the idea of a period of time [24?48? hours] during which anyone on the PMC may -1 the release plan. This works well I think if at least the person on the project who makes the request to the PMC is also on the PMC. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: oro-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: oro-dev-help@jakarta.apache.org