All software has bugs but we we should really have some faith in our automated testing suite. The 0 in 5.3.0 already indicates it's the first release of 5.3 line and as such may have some features that are not as well field tested than say, features in 5.2.6 release. Version resolution works best if the version consists only of numbers. We don't have an internal alpha/beta process and as such, any label we add to the version is purely subjective. This is not an end user application but a framework, any drastic issues are very likely to be discovered during development of the web application. Many of the more popular open source projects use just a running build number (Jenkins, Jitsi, etc.) and they seem to be doing fine with that. If we cranked out RCs, who would really put the effort to thoroughly manually test them? If we just voted on them on the "yes, I've tried it" basis the only thing we'd be adding is bureaucracy. Just my two cents and sorry for the rant but my years in a big corporate have made me quite allergic to resource waste.
Kalle On Thu, Jun 23, 2011 at 5:25 AM, Thiago H. de Paula Figueiredo <[email protected]> wrote: > On Thu, 23 Jun 2011 05:15:47 -0300, Ulrich Stärk <[email protected]> wrote: > >> I guess we can continue as before. The only thing I'd like to see changed >> is the addition of the >> status of the release to the version number. I.e. alpha, beta, ... > > Agreed. I'd just leave the stable releases without suffixes and append > alpha, beta, rc or something like that to emphasize that a release isn't > stable. > > To me, the last vote was confusing: it says "5.3.0" without any indication > that it isn't a stable release. Anyone that doesn't follow the dev list > would probably think it's a stable release, I guess. > > -- > 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]
