commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <>
Subject Re: [lang] process question: fixing bug on the fly
Date Wed, 09 Apr 2003 19:01:50 GMT

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.


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                     
> Purple Technology - Code and Consulting
> jGuru - Java News and FAQs       
> Gamelan - the Original Java site 
> Stinky - Art and Angst           
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message