RE: Milestone builds?

[Abrams, Howard A]

+1 for:   nightly + votes = M1 nightly + votes = M2 . . M[n] + votes + branch = RC1 RC1 + bug fixes = RC2 RC2 + bug fixes = RC3 . . RC[n] + votes -> 1.[n]     [SNIP]   > A milestone release could even be just a nightly build renamed (or maybe > not even renamed). They would be created whenever people feel that (a) > there has been significant progress from the last milestone in new > features or bugfixes and (b) the code seems to be fairly stable. >    [SNIP]   > > > > Also, I would suggest that we follow the Struts procedure and > > eventually vote one of these milestone builds to be an official GA > > release (we would subject it to TCK before then.) > > +1 > > Having milestone releases available means a larger user community will > be using them, and therefore there's more confidence that all > showstoppers are known. It would be great to be able to promote "M99" to > "RC1" to "1.x" in the knowledge that it is actually in real use out in > the world. >