Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 40654 invoked from network); 18 Sep 2002 21:17:02 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 18 Sep 2002 21:17:02 -0000 Received: (qmail 3776 invoked by uid 97); 18 Sep 2002 21:17:41 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 3752 invoked by uid 97); 18 Sep 2002 21:17:41 -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 3740 invoked by uid 98); 18 Sep 2002 21:17:40 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Content-Type: text/plain; charset="iso-8859-1" From: Steve Downey To: "Jakarta Commons Developers List" Subject: Re: Release Was: [lang] Builders complete? Date: Wed, 18 Sep 2002 17:14:46 -0400 User-Agent: KMail/1.4.1 References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200209181714.46344.steve.downey@netfolio.com> 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 Wednesday 18 September 2002 08:21 am, Henri Yandell wrote: > On Tue, 17 Sep 2002, Steve Downey wrote: > > No one had volunteered yet. > > I'm happy to. Had been giving everyone time to play with builders as th= ey > weren't something I had a great itch for. > > There are a lot of things we have on the post-release list, and Stephen= 's > got a good thing going in the STATUS.html to show post release ideas. I > suggest we all continue to add issues and ideas to that to signify thin= gs > we itch/care about, such as your introspection Steven. It's Steve who's got the introspection itch. Steven will have to scratch = his=20 own itches. > > Daniel's volunteered to handle the actual CVS whatnot. Tagging and > branching and whittling into shape, so it seems our process is: > > 1) Decide on what we want to go and what doesn't go. What's there now + Steven's planned fixes for exceptions? > 2) All agree that we're happy with the state of what is going, includin= g > javadoc and unit tests. There's work to be done on the javadocs. Nothing crippling, but it could = be=20 better. The unit tests seem to be pretty good, though. > 3) Make a preliminery build available internally. I'd like to then run > JDiff on this with the beta. This hopefully can make us aware of any > issues. This means having tag stuff in cvs done at this point. > 4) Propose a vote for a 1.0 release. > 5) Worry about the website. I doubt we'll be doing a lot in the way of > tutorials or docs etc, but we need to make sure the simple bits we h= ave > there are good. > 6) Ensure we are in Bugzilla. I'm not sure if we are yet. > 7) Release. > > Does this sound right to everyone? > > Hen Sounds good to me. -- To unsubscribe, e-mail: For additional commands, e-mail: