I think the underlying problem is the use of the term "release" for non-production-quality code. It shouldn't be necessary to have one particular version identified as the "stable version". If it isn't fully stable, then it should be a "release candidate", not a "release".
Just my 2 cents. I know that's not how the community's release process goes. On Wed, Jun 22, 2011 at 7:46 PM, Howard Lewis Ship <[email protected]> wrote: > I've been noticing that "release" is a bit overload. > > We have a product, "Tapestry" or "Apache Tapestry", or "Tapestry 5". > > We have versions, such a 5.2.6 or 5.3.0. > > We have releases such as 5.2 or 5.3. > > However, something seems odd in the phrase "We are pleased to announce > the release of Tapestry 5.2.6, the new stable version of Tapestry > 5.2.". Actually, that reads well. But I keep having problems > elsewhere with the verb "release" vs. the noun "release" (as a > sequence of versions). Is it confusing anyone else? Is there a > better set of terms we should stick with? > > -- > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
