Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 64691 invoked from network); 17 Dec 2002 04:55:55 -0000 Received: from exchange.sun.com (HELO nagoya.betaversion.org) (192.18.33.10) by daedalus.apache.org with SMTP; 17 Dec 2002 04:55:55 -0000 Received: (qmail 10598 invoked by uid 97); 17 Dec 2002 04:57:10 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 10516 invoked by uid 97); 17 Dec 2002 04:57:10 -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 10487 invoked by uid 98); 17 Dec 2002 04:57:09 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Mon, 16 Dec 2002 20:55:47 -0800 (PST) From: "Craig R. McClanahan" To: Jakarta Commons Developers List Subject: Re: GenerateUniqueId.java In-Reply-To: <3DFE83E0.70400@apache.org> Message-ID: <20021216205039.E67510-100000@icarus.apache.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 1.6.2 0/1000/N 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 Mon, 16 Dec 2002, Sam Ruby wrote: > Date: Mon, 16 Dec 2002 20:54:40 -0500 > From: Sam Ruby > Reply-To: Jakarta Commons Developers List > To: commons-dev@jakarta.apache.org > Subject: Re: GenerateUniqueId.java > > dion@multitask.com.au wrote: > > > > I think Gump is the best tool we have for doing this, and we need to be > > nicer citizens. > > > > Having just been bitten by HttpClient deleting methods that have been > > available for months in CVS, I'm starting to question the current process > > of only deprecating if a method has been available in a 'release' product. > > > > I would like deprecation to happen for a time period before deletion, if > > the code was not part of a release, especially in Commons, where the code > > is by design meant to be used by others. And the code base can be stable, > > without a release for a long time. > > > > Bless you dIon. > > More frequent releases and/or policies like you describe would help. > > But mostly, we need people to care and work together. > I agree that "working together" is important. IMHO, that includes a few more steps by the people that extract a reusable chunk of code from some other project into a sandbox module -- if the originating project adopts a dependency on a sandbox project, there's a fair degree of "shame on you" for them as well as for people working on the sandbox library. And yes, I'm currently in the same boat on one of my big projects (Struts HEAD depends on commons-resources from the sandbox). The difference is that there is no way I'd ever do a final release of Struts 1.1 without having commons-resources promoted to the Commons and released (or removing the dependency). > - Sam Ruby > Craig McClanahan -- To unsubscribe, e-mail: For additional commands, e-mail: