You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Lee Peik Feng <pf...@syabas.com> on 2002/08/05 11:28:26 UTC
Tomcat 4.1.8
I'm just curious why is Tomcat 4.1.8 beta released before 4.1.7 released? As
Tomcat 4.1.7 still in beta.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Tomcat 4.1.8
Posted by Lee Peik Feng <pf...@syabas.com>.
Thank you for clarify my doubt.
----- Original Message -----
From: "Craig R. McClanahan" <cr...@apache.org>
To: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Tuesday, August 06, 2002 12:01 AM
Subject: Re: Tomcat 4.1.8
>
>
> On Mon, 5 Aug 2002, Lee Peik Feng wrote:
>
> > Date: Mon, 5 Aug 2002 17:28:26 +0800
> > From: Lee Peik Feng <pf...@syabas.com>
> > Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> > To: Tomcat Users List <to...@jakarta.apache.org>
> > Subject: Tomcat 4.1.8
> >
> > I'm just curious why is Tomcat 4.1.8 beta released before 4.1.7
released? As
> > Tomcat 4.1.7 still in beta.
> >
>
> Tomcat 4.1 is using the same release management scheme that is used for
> the Apache web server itself:
>
> * Periodically a point release (4.1.x) is created and made
> available for testing, with no labelling of quality
> ("alpha", "beta", or whatever). You've probably seen
> Remy's postings about 4.1.x releases being "made available
> for testing" -- that is done only here and on TOMCAT-DEV
> to provide people a chance to download and try the latest
> point release.
>
> * After people have had a chance to test, a vote is taken on
> TOMCAT-DEV to decide what to do with that particular release:
> - Mark it "alpha" quality if it sort of works, but has problems
> (also triggers announcement to the world)
> - Mark it "beta" quality if it seems to work well
> (also triggers announcement to the world)
> - Throw it away if showstopper bugs were encountered
>
> * Eventually, a point release will be found to be of such high
> quality that it gets voted as suitable for "general availability"
> and announced to the world as a stable release. For Apache 2.0,
> it took roughly 35 point releases to get to this point (and over
> two years). Hopefully, we'll be able to get there faster :-),
> but aggressive testing of new point releases is the best way to
> help that happen.
>
> So, 4.1.7 itself never will be "released" -- 4.1.8 is just the next stage
> in the evoluation of the 4.1 code base. If you want to stay with betas,
> just grab the latest 4.1.x release announced as "beta" and you will pick
> up all the accumulated improvements.
>
> Craig
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Tomcat 4.1.8
Posted by "Craig R. McClanahan" <cr...@apache.org>.
On Mon, 5 Aug 2002, Lee Peik Feng wrote:
> Date: Mon, 5 Aug 2002 17:28:26 +0800
> From: Lee Peik Feng <pf...@syabas.com>
> Reply-To: Tomcat Users List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Subject: Tomcat 4.1.8
>
> I'm just curious why is Tomcat 4.1.8 beta released before 4.1.7 released? As
> Tomcat 4.1.7 still in beta.
>
Tomcat 4.1 is using the same release management scheme that is used for
the Apache web server itself:
* Periodically a point release (4.1.x) is created and made
available for testing, with no labelling of quality
("alpha", "beta", or whatever). You've probably seen
Remy's postings about 4.1.x releases being "made available
for testing" -- that is done only here and on TOMCAT-DEV
to provide people a chance to download and try the latest
point release.
* After people have had a chance to test, a vote is taken on
TOMCAT-DEV to decide what to do with that particular release:
- Mark it "alpha" quality if it sort of works, but has problems
(also triggers announcement to the world)
- Mark it "beta" quality if it seems to work well
(also triggers announcement to the world)
- Throw it away if showstopper bugs were encountered
* Eventually, a point release will be found to be of such high
quality that it gets voted as suitable for "general availability"
and announced to the world as a stable release. For Apache 2.0,
it took roughly 35 point releases to get to this point (and over
two years). Hopefully, we'll be able to get there faster :-),
but aggressive testing of new point releases is the best way to
help that happen.
So, 4.1.7 itself never will be "released" -- 4.1.8 is just the next stage
in the evoluation of the 4.1 code base. If you want to stay with betas,
just grab the latest 4.1.x release announced as "beta" and you will pick
up all the accumulated improvements.
Craig
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>