You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Craig R. McClanahan" <cr...@apache.org> on 2002/06/12 19:33:07 UTC
Re: Two TCs???
On Wed, 12 Jun 2002, Pae Choi wrote:
> Date: Wed, 12 Jun 2002 12:56:20 -0700
> From: Pae Choi <pa...@earthlink.net>
> Reply-To: Tomcat Developers List <to...@jakarta.apache.org>
> To: Tomcat Users List <to...@jakarta.apache.org>
> Cc: Tomcat Developers List <to...@jakarta.apache.org>
> Subject: Two TCs???
>
> Do we have two seperate TCs in the development process?
>
> I see the v4.0.4-b3 release arouind 10th and 11th of May as
> well as v4.1.3-b release around 28th and 29th of May.
>
Active development of new features (such as substantially improved
performance on JSP pages, and the new admin webapp) are taking place in
the 4.1.x development tree. Because there is lots of new code here, the
risk of new bugs is somewhat higher than on a stable release.
Bugfix maintenance releases continue in the 4.0.x development tree so that
people running production apps have a lower risk way to incorporate fixes
for existing bugs -- but new features only go into the new version.
> What's going on?
>
Same thing that happens in most major software development projects --
overlapping development cycles. Consider Apache (1.3.x versus 2.0.x),
Linux (2.4 versus 2.5), and pretty much any other large scale product, and
you'll see the same thing.
>
> Pae
Craig
>
>
> [1] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b3/
> [2] http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.3-beta/
>
>
>
> --
> 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: Two TCs???
Posted by Pae Choi <pa...@earthlink.net>.
Craig,
Thank you for your reply as well as clarifying my previous inquiry.
Best,
Pae
----- Original Message -----
From: "Craig R. McClanahan" <cr...@apache.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Cc: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Wednesday, June 12, 2002 10:33 AM
Subject: Re: Two TCs???
>
>
> On Wed, 12 Jun 2002, Pae Choi wrote:
>
> > Date: Wed, 12 Jun 2002 12:56:20 -0700
> > From: Pae Choi <pa...@earthlink.net>
> > Reply-To: Tomcat Developers List <to...@jakarta.apache.org>
> > To: Tomcat Users List <to...@jakarta.apache.org>
> > Cc: Tomcat Developers List <to...@jakarta.apache.org>
> > Subject: Two TCs???
> >
> > Do we have two seperate TCs in the development process?
> >
> > I see the v4.0.4-b3 release arouind 10th and 11th of May as
> > well as v4.1.3-b release around 28th and 29th of May.
> >
>
> Active development of new features (such as substantially improved
> performance on JSP pages, and the new admin webapp) are taking place in
> the 4.1.x development tree. Because there is lots of new code here, the
> risk of new bugs is somewhat higher than on a stable release.
>
> Bugfix maintenance releases continue in the 4.0.x development tree so that
> people running production apps have a lower risk way to incorporate fixes
> for existing bugs -- but new features only go into the new version.
>
> > What's going on?
> >
>
> Same thing that happens in most major software development projects --
> overlapping development cycles. Consider Apache (1.3.x versus 2.0.x),
> Linux (2.4 versus 2.5), and pretty much any other large scale product, and
> you'll see the same thing.
>
> >
> > Pae
>
> Craig
>
>
> >
> >
> > [1]
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b3/
> > [2]
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.3-beta/
> >
> >
> >
> > --
> > 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>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Two TCs???
Posted by Pae Choi <pa...@earthlink.net>.
Craig,
Thank you for your reply as well as clarifying my previous inquiry.
Best,
Pae
----- Original Message -----
From: "Craig R. McClanahan" <cr...@apache.org>
To: "Tomcat Developers List" <to...@jakarta.apache.org>
Cc: "Tomcat Users List" <to...@jakarta.apache.org>
Sent: Wednesday, June 12, 2002 10:33 AM
Subject: Re: Two TCs???
>
>
> On Wed, 12 Jun 2002, Pae Choi wrote:
>
> > Date: Wed, 12 Jun 2002 12:56:20 -0700
> > From: Pae Choi <pa...@earthlink.net>
> > Reply-To: Tomcat Developers List <to...@jakarta.apache.org>
> > To: Tomcat Users List <to...@jakarta.apache.org>
> > Cc: Tomcat Developers List <to...@jakarta.apache.org>
> > Subject: Two TCs???
> >
> > Do we have two seperate TCs in the development process?
> >
> > I see the v4.0.4-b3 release arouind 10th and 11th of May as
> > well as v4.1.3-b release around 28th and 29th of May.
> >
>
> Active development of new features (such as substantially improved
> performance on JSP pages, and the new admin webapp) are taking place in
> the 4.1.x development tree. Because there is lots of new code here, the
> risk of new bugs is somewhat higher than on a stable release.
>
> Bugfix maintenance releases continue in the 4.0.x development tree so that
> people running production apps have a lower risk way to incorporate fixes
> for existing bugs -- but new features only go into the new version.
>
> > What's going on?
> >
>
> Same thing that happens in most major software development projects --
> overlapping development cycles. Consider Apache (1.3.x versus 2.0.x),
> Linux (2.4 versus 2.5), and pretty much any other large scale product, and
> you'll see the same thing.
>
> >
> > Pae
>
> Craig
>
>
> >
> >
> > [1]
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4-b3/
> > [2]
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.3-beta/
> >
> >
> >
> > --
> > 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>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>