The 1.2.1 and 1.2.2 test builds didn't make it to releases. That is as it should be - we want releases to be quality builds.
What I feel very strongly about is that nothing should be called a Release until we vote on it, especially since I believe this is an ASF requirement. We have said that anyone can build a Test Build (e.g. 1.2.x) at any time, and that's fine. But I don't want to see such a build viewed as a Release by the community if the developers / PMC haven't sanctioned it by a vote.
I think ultimately we agree even more than I realized, since, looking back at how you describe these events, I realize that my main concern - version number confusion - is not at issue.
I simply think of anything with a version number as a release. I'm happy to change that and to describe the first output of the "release process" as a "test build" instead of an "alpha release".
In fact, I'd be +1 to that, given that we have two cases in recent memory where the artifact was not really even usable as an alpha release.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn back; I'll know I'm in the wrong place."
- Carlos Santana
