Hello,
We'd like to create an MMBase-1.6.1 release somewhere around the 20th of
January. Exact time and date will be announce next week.
But before the release, the releasenotes must be updated with the latest
fixes. I allways like to see what changes are done in which release, so
I know what fixes are the most recent. There are a few ways we could do
this:
- add a version tag to every line in the releasenotes (as it was/is done
in MMBase-1.5.x and Tomcat 4.1.x) , eg:
[1.6.0] fixed bug blablabla
[1.6.1] fixed bug blablablabla
- create groups of notes, eg:
[1.6.0]
- fixed bug bla
- fixed bug bladerdebla
[1.6.1]
- fixed bug bla2
- add a date to a note, eg:
[20021215] fixed bug bla
[20030113] fixed bug blabla
I'd like the first one the best, but I'd like to hear which one do you
like? I don't think the second is very usefull, because there are
allready groups of notes in the releasenotes (they are grouped by
category, eg taglib, security, etc). Or we have to remove these groups....
I'm not asking for a vote, I just want to discuss this and maybe after
this call for a vote.
I also like to state that it's very important to keep the releasenotes
uptodate. If you fix a bug or add a new feature (only for cvs-head),
please add it to the releasenotes.
Gerard
- Re: [MMBase-1.6.1] Update Gerard van Enk
- Re: [MMBase-1.6.1] Update Pierre van Rooden
- Re: [MMBase-1.6.1] Update Rob van Maris
- Re: [MMBase-1.6.1] Update Gerard van Enk
- Re: [MMBase-1.6.1] Update Rob Vermeulen
- Re: [MMBase-1.6.1] Update Pierre van Rooden
- Re: [MMBase-1.6.1] Update Gerard van Enk
- Re: [MMBase-1.6.1] Update Pierre van Rooden
- Re: [MMBase-1.6.1] Update Gerard van Enk
- Re: [MMBase-1.6.1] Update Rob Vermeulen
