Release is a release, especially given that it's all in the open - i.e. there's no hidden internal process to produce release candidates to a subset of users leading to a GA release. Re-wording your sentence to: "We are pleased to announce a maintenance release of Apache Tapestry 5, version 5.2.6." You could continue with "... for the stable T5.2 line" but seems unnecessary to me since the version number already indicates the product line it's for. Perhaps I'm advocating the use of "product line" as a more consumer-friendly term for a branch in cases where using a release (the noun) would be too confusing.
I think Apache branding guidelines in fairly strict terms require using "Apache This" or "Apache That" when speaking about Apache projects and products. Kalle On Wed, Jun 22, 2011 at 4: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]
