I'm content with calling it 5.3.0. It's the first release on the 5.3 code base. Even calling something "final" is kinda weird, imo. Like, 5.2.5 was "final"...except we released 5.2.6... The only way to declare something final is retrospectively: look, we didn't make any more 5.0 releases; I guess 5.0.19 was final... at least for now.
As for "alpha"... I think 5.3.0-SNAPSHOT fulfills that role, personally. Now we have 5.3.1-SNAPSHOT; those builds are the "alpha" builds of the 5.3.1 release. Robert On Jun 24, 2011, at 6/242:20 PM , Thiago H. de Paula Figueiredo wrote: > Hi, Kalle! > > I wasn't clear with my words: I don't think 5.3.0 isn't production-ready now. > I haven't even used it yet :'(, so I can't say anything bad about it. I meant > 5.3.0 is not final. > > 5.3.0, now, is an alpha release, so I think the version and JAR names should > have some suffix about it somehow. The JBoss conventions, for example, are > these (http://community.jboss.org/wiki/JBossProjectVersioning): > > major.minor.micro.Alpha[n] > major.minor.micro.Beta[n] > major.minor.micro.CR[n] > major.minor.micro.Final > > I don't like suffixes for final versions nor the use of uppercase letters nor > I think Tapestry needs 4 release stages (just alpha or beta and final, > besides snapshots, should be enough), but I guess we could adapt it. > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and > instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
