From commons-dev-return-46993-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org Mon Mar 01 13:39:25 2004 Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 24793 invoked from network); 1 Mar 2004 13:39:25 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 1 Mar 2004 13:39:25 -0000 Received: (qmail 32458 invoked by uid 500); 1 Mar 2004 13:39:18 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 32415 invoked by uid 500); 1 Mar 2004 13:39:18 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 32401 invoked from network); 1 Mar 2004 13:39:18 -0000 Received: from unknown (HELO umbongo.flamefew.net) (64.253.103.114) by daedalus.apache.org with SMTP; 1 Mar 2004 13:39:18 -0000 Received: by umbongo.flamefew.net (Postfix on Linux (i386), from userid 500) id B30BC1AE7; Mon, 1 Mar 2004 08:39:15 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by umbongo.flamefew.net (Postfix on Linux (i386)) with ESMTP id B1E9B1AD8 for ; Mon, 1 Mar 2004 08:39:15 -0500 (EST) Date: Mon, 1 Mar 2004 08:39:15 -0500 (EST) From: Henri Yandell X-X-Sender: hen@umbongo.flamefew.net To: Jakarta Commons Developers List Subject: Re: [releases] lacking releases for .... Was: [sandbox] report In-Reply-To: <8E868D4A-6B81-11D8-BF57-000A95A01192@4quarters.com> 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: minotaur-2.apache.org 1.6.2 0/1000/N On Mon, 1 Mar 2004, Geir Magnusson Jr wrote: > > On Feb 29, 2004, at 11:26 AM, Henri Yandell wrote: > > > Does anyone have estimated release dates for these? and who is release > > manager for each one? [something we should probably make a clause of > > sandbox->proper promotion]. If the release manager then vanishes, we > > should demote if no one else volunteers. > > Subtle point - should there be a required release to get to commons out > of sandbox? One issue we're discussing is that code shouldn't depend > on sandbox code, as it's supposed to be just a 'play area'. That said, > having users is a great way to clean, refactor and evolve code, so if > you can only get to commons from sandbox w/ a release, then we are > imposing a bit of a chicken-egg problem, or just releasing for the sake > of release, which I think is pointless. I think this is pretty much the current situation. For most components, they move from sandbox to commons with the intention of a release. A few have just got hung up at the last hurdle :) Hen --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org