A few remarks. There are 111 open Bugzilla entries for Cocoon 2. It should be possible for everyone to quickly find all of those open issues which require a resolution for the release of 2.1.
All open bugs with submitted patches should be resolved for the next release. An exception might be those patches which were submitted very recently. In any case issues not resolved should at least be deliberately postponed and not left unattended. Currently 33 patches are waiting for inclusion. Some of them are pretty old. It is demotivating to see that people fix bugs but that their fixes are not used. Why should someone try to fix any of the other bugs? Only committers can merge the code. As far as I see it it is one of the main responsibilities of a release manager to deal with this task. I therefore again propose the following (copied from a mail sent a month ago): "1.) two [Bugzilla-]Milestones are added: 2.1 and 2.2 2.) all of the [other] planned items [which were mentioned on Release Plan page for 2.1 Beta] which have not yet been finished are entered into Bugzilla 3.) all open Bugzilla-entries are assigned to either Milestone 2.1 or 2.2" Andreas ----- Original Message ----- From: "Carsten Ziegeler" <[EMAIL PROTECTED]> To: "Cocoon-Dev" <[EMAIL PROTECTED]> Sent: Friday, May 30, 2003 8:12 AM Subject: Release Plan for 2.1 > AFAIK, the only open issue for making a beta is the FOM, right? > I would suggest, that we make a milestone three on the 10th of > June unless the FOM API is stable. If it's stable by then, > we could make a beta 1 then. > > What do you think? > > Carsten > > Carsten Ziegeler > Open Source Group, S&N AG > http://radio.weblogs.com/0107211/ >
