we voted a 5.2.0 release. Yes its alpha, but the point is to get it out there. If the code was perfect, we would retroactively vote it beta and then GA. Instead we'll likely have a 5.2.1 pretty soon.
We followed the established Apache practice of vote to release, then vote for stability. In the past, we tried to have countdown releases (RC-1, RC-2, then GA). And we'd always have to follow up the GA with a bug patch release. Giving the release exposure THEN voting on its stability solves that problem. On Wed, Aug 18, 2010 at 10:14 AM, Christian Edward Gruber <[email protected]> wrote: > Um... hey all, > > I'm a little behind in both e-mail and my plans. Why do I see released > projects/jars/poms on repo1? I thought we were at 5.2.0-alpha. Are we > treating .0 as alpha, .1 as a beta, etc., until we have a release? > > Christian. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
