William A. Rowe, Jr. wrote:
Anytime a committer wants, they are absolutely free to tag the tree and tar the build. But at that moment, it's a 'plain old tarball', it's not a release (even if there was a vote beforehand like this one.)
FYI - there's a reason for this. Even if there are competing interests, nobody can single handedly block another release, or even a small minority. Putting releases into user's hands is what the ASF is all about. Good ones we hope :) It might seem arcane, but this is based on the collective wisdom of the original httpd group to ensure that when there are times that folks are generally being disagreeable, at least the project cannot be frozen solid. I'm glad the Tomcat project is really working twords similar goals and we don't have any of that hassle here; but it's good to keep using the same pattern so that even if there were disagreements in the future, it's possible to keep the project flowing. Oh - and this isn't the same as releasing vetoed code. If you want to cut a release, and someone's commit has a veto outstanding, simply tag the version before the debated code was added. Again not a problem here lately, and that's a good thing. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]