Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 37285 invoked from network); 9 Apr 2003 19:01:54 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 9 Apr 2003 19:01:54 -0000 Received: (qmail 6212 invoked by uid 97); 9 Apr 2003 19:03:49 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@nagoya.betaversion.org Received: (qmail 6205 invoked from network); 9 Apr 2003 19:03:49 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 9 Apr 2003 19:03:49 -0000 Received: (qmail 36815 invoked by uid 500); 9 Apr 2003 19:01:48 -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 36719 invoked from network); 9 Apr 2003 19:01:47 -0000 Received: from umbongo.flamefew.net (64.253.103.114) by daedalus.apache.org with SMTP; 9 Apr 2003 19:01:47 -0000 Received: by umbongo.flamefew.net (Postfix on Linux (i386), from userid 500) id A9F0B3A2482; Wed, 9 Apr 2003 15:01:50 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by umbongo.flamefew.net (Postfix on Linux (i386)) with ESMTP id A8D35296E95; Wed, 9 Apr 2003 15:01:50 -0400 (EDT) Date: Wed, 9 Apr 2003 15:01:50 -0400 (EDT) From: Henri Yandell X-X-Sender: To: Jakarta Commons Developers List , Subject: Re: [lang] process question: fixing bug on the fly In-Reply-To: <20030409115223.C10697@stinky.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: daedalus.apache.org 1.6.2 0/1000/N Just make sure you mention it in the cvs comment. I don't know about other projects, or other people, but when I do a release [and unless anyone is against it, I'm happy to volunteer to do 2.0] I immediately generate a cvs changelog, remove everything before the previous release and analyse every comment. I then edit release-notes at that point. So release-notes tends to be the last released one. I pay enough attention to try to match bug numbers to cvs comments. In fact, it'd probably help the most if people mentioned bug numbers in their cvs comments. Not a biggy though. Hen On Wed, 9 Apr 2003, Alex Chaffee / Purple Technology wrote: > While converting the string escape routines to use uppercase, I > discovered and fixed a bug in the original unescape. (If a string to > be unescaped ended with a unicode escape, it would discard it.) > > Since this bug existed in 1.0, I'm not sure what the right procedure > is for making sure this bugfix gets into the release notes or other > documentation, so upgrading users are aware of it. > > Should I file a bug report and close it immediately? > > Should I add it to RELEASE-NOTES.txt? That file seems to be out of > date... > > Thanks - > > - Alex > > -- > Alex Chaffee mailto:alex@jguru.com > Purple Technology - Code and Consulting http://www.purpletech.com/ > jGuru - Java News and FAQs http://www.jguru.com/alex/ > Gamelan - the Original Java site http://www.gamelan.com/ > Stinky - Art and Angst http://www.stinky.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-dev-help@jakarta.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org