-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter,

On 8/25/2010 10:30 AM, Peter Crowther wrote:
> On 25 August 2010 15:23, Christopher Schultz
> <ch...@christopherschultz.net>wrote:
> 
>> Again, this is partly because I feel a certain sense of order which
>> requires releases to be X.0.0.
>>
>> Why?  And by "release" do you mean "stable, production-quality releases
> that we'll stake our reputations on" (in which case almost every x.0.0 would
> in reality fail the test) or do you mean "released outside the development
> team"?
> 
> Not saying it's "wrong" (I tend to avoid "right" and "wrong" due to
> relativism), just interested by the expectation.

Microsoft products notwithstanding, I kind of expect that release X.0.0
will be appropriate for general-purpose use. That wasn't true of 6.0.0
and 7.0.0. One had to wait around until 6.0.1 or 6.0.10 or whatever
before 6.0.x was really "ready". I'm sure there will be an announcement
at some point that 7.0.5 (or whatever it happens to be) is stable (no
API changes) and production-quality in that no correctness tests fail,
but it would be nice to just /know/ that 7.0.0 is "the release" and
everything after that is bugfixes and stuff. Instead, 7.0.5 (or
whatever) will be "the release" which is just... surprising.

It's not really tripping me up: don't worry. I'm thinking about casual
readers/downloaders who don't see the "beta" in the name (which, by the
way, only appears in a single place on
http://tomcat.apache.org/download-70.cgi, with no specific warning about
how it's a beta release and not appropriate for production).

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkx1L/cACgkQ9CaO5/Lv0PCihgCcDLX2J5RWx+M9rB1R/tLLuvMI
m4oAn0WCXF4ajP1MK/3bBpyB1Ut+4lkt
=nCnY
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to