Re: [MMBase-1.6.0] Releaseplan Proposal

[Gerard van Enk]

Eduard Witteveen wrote:

	Bugs:
++ status may only change after discussion on the list?

??? If a bug is fixed it will be closed...
Not sure what you mean here.

++ bugs will be posted and may only be changed by release

team members
Why can somebody else not post a bug?

That all bugs have to be verified by the release team, if they are
there, and it has to be verified if the fix is sufficient(or if it is
valid to let it be a bug (by changing the bug, I mean changing the
status of the bug)).
I never did say an bug shouldn't be posted.

IMHO that's something the commitors allways have to do, not only before a release. Bugs added to the bugtracker need to be checked by a commitor, added to a maintainer, etc.

	During this code freeze most outstanding bugs must be fixed and
	stability must be tested.
++ When not, freeze will be extended..

just because we branch, doesn't mean you won't add bugfixes.
We need and end date for teh freeze so other projects (Query,
Media) can start adding and testing their code to cvs head.

Disagree, we have to branch when most bugs are fixed(or simply are
accepted). This will create a much better release imho, and freeze
period will be much shorter, since it will mean that everyone has to fix
the bugs before adding new functionality.
When all know bugs are solved, or accepted, we should branche and not
before that point(since that would also mean every bug fix has to be
done inside 2 branches).

IMHO it somewhere in between....So not have a hard deadline, but also no deadline at all.

Gerard