The Apache way, which I like, is to evaluate a release's stability AFTER it is out in user's hands. Thus we vote to release a version, say 5.3.217, and after its been out and in use, we vote to upgrade it from "beta" (or even "release candidate") to final/stable/GA (choose your term). I think its a good system, that reflects the reality of complex code and leveraging the community to discover problems.
On Wed, Jun 22, 2011 at 5:40 PM, ael <[email protected]> wrote: > In Netbeans > > Release Candidate RC1 > > > Release Candidate RC2 > > > Final Release > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/A-question-of-vocabulary-release-vs-version-vs-tp4515917p4515999.html > Sent from the Tapestry - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > 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]
