commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig McClanahan <>
Subject Re: [digester] TO-DO for release 1.6
Date Thu, 15 Apr 2004 00:41:21 GMT
robert burrell donkin wrote:

>> * prepare release notes
>>   I'm willing to do this if someone can give me some hints on the
>>   most efficient way to do this...
> hehehe
> by tradition, digester uses criag's way of preparing release notes. 
> this means going through and collating the messages from each cvs 
> commit message and cross indexing them into features and bug fixes. 
> though a little labourious, it is a very good way of learning why good 
> cvs comments are important :)
> unfortunately, i do get a little lazy from time to time, so here's my 
> prior apologies. (i will give detail instructions on the mechanics if 
> you need them.)
> betwixt uses continuous addition. this works out well (and plays very 
> nicely with google) but does slow development. every feature is not 
> only added, unit tested but also written up and added to the list of 
> notes. both are good systems with different advantages.

If I were disciplined like Robert, I'd use continuous addition too :-).  
Unfortunately, I'm more a typical developer in this particular respect.

> - robert


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

View raw message