- the part about the release is not the way we currently do the releases Here we have to decide if we want to stick to our "more lazy" approach of releases or if we want to adopt a more formal but improved way of releasing Cocoon.
I was thinking of down-playing the importance of the process, simplifying it into:
* someone meritocraticaly becomes Release Manager, lazy consensus applies and people are free to self.propose()
* that person prepares a release plan with work items
* once these items are resolved (lazy resolution, consensus votes when necessary), that person comes up with a release vote
* release vote requires majority approval
* off we go
What do you think? Too little formality?
</Steven> -- Steven Noels http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/stevenn/ stevenn at outerthought.org stevenn at apache.org
