On Wed, 20 Nov 2002, Steinar Bang wrote:
If one looks at the distribution directory of tomcat, it is easy to
get confused. It contains the directories:
v4.0.5/ 09-Oct-2002 07:28-
v4.0.6/ 08-Oct-2002 08:27-
v4.1.12/02-Oct-2002 03:01-
v4.1.15-alpha/ 14-Nov-2002 00:48-
Ie. there's a 4.1.12, no 4.1.13, or 4.1.14, but instead a 4.1.15 that
is marked alpha. The immediate question is: is this an alpha of a
final 4.1.15 release? Or is 4.1.15 an alpha release of the final
version of 4.1.x?
A bit of googling found me
URL:http://www.faqchest.com/prgm/tomcat-l/tmct-02/tmct-0208/tmct-020879/tmct02082620_30399.html
And I guess the answer is sort of the first one, and sort of the last
one. Ie. if 4.1.15-alpha turns out to be a stable release, the
-alpha will be yanked from the version number, and 4.1.15 will
become a production release.
Yep.
However, if 4.1.15 isn't found good enough, it will be completely
yanked from the distribution directory, and consigned to the scrapheap
of history. And then a new version 4.1.16-alpha will be announced.
I'm still a little confused, but I guess that whatever 4.1.x with
x=14 is finally released, will have a working
HttpServletRequest.isSecure() when using the Coyote Ajp1.3 connector.
Tomcat 4.1 is following the same basic release policy that the Apache
HTTPD server, and several other Jakarta projects, are using. Milestone
releases happen regularly, and go out with a default state of alpha.
After some evaluation time, the milestones might get voted (by the
committers, based on user feedback) as beta or general release
quality. There is not any such thing as the final release of 4.1.x
(until people stop working on it, which would only happen if a subsequent
4.2.x or 5.0.x release was pretty solid) -- only the latest production
release, which is currently 4.1.12.
Craig
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
