<Gerard van Enk:> > 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.
I'm glad to see minor releases are getting more attention and planning ahead. > 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: I prefer the first option as well. What about changes in several branches, are these to be specified for different versions (e.g. 1.6.1 and 1.7), or are updates to minor releases supposed to apply to the next major release implicitly? I prefer explicit notes. > 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. This is new to me, I've always assumed that the releasenotes are compiled by the release-team. Maybe these practices should be documented to guide new developers. Rob van Maris Senior Developer Finalist IT Group Java Specialists ------------------------------------------------------------- Amsterdam, The Netherlands Office: +31 20 5962321 (Direct) Mobile: +31 651444006 Fax: +31 20 5962331 -------------------------------------------------------------
