tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Saegesser" <marc.saeges...@apropos.com>
Subject RE: 3.2.2 Release?
Date Fri, 02 Feb 2001 20:44:02 GMT
You are correct, tomcat_32 is the appropriate tag.  tomcat_32 is a branch
tag so if you use cvs to check out jakarta-tomcat like

cvs co -r tomcat_32 jakarta-tomcat

then you'll get the latest version of all files on this branch.  This is
referred to as the "tip" of the branch.

The labels like tomcat_32_final and tomcat_321_final label a particular
version of a file so the command

cvs co -r tomcat_321_final jakarta-tomcat

will retrieve the versions of all the files that make up the Tomcat 3.2.1
release.

The code that is (most likely) destined to become Tomcat 3.3 is the main
branch of the repository, often referred to as the "HEAD".  To get this code
from cvs use a command like

cvs co jakarta-tomcat

When Tomcat 3.3 is released a new branch will be created called tomcat_33
and this will form the basis for all bug fixes and patches for the 3.3
release.  The HEAD will then become the code base for any new feature
development of the 3.x repository.

> -----Original Message-----
> From: David Weinrich [mailto:dweinr1@home.com]
> Sent: Friday, February 02, 2001 2:31 PM
> To: Tomcat Dev List
> Subject: Re: 3.2.2 Release?
>
>
> On a somewhat unrelated note...
>   I noticed a bugrat report this morning on an urlencoding that I had
> submitted a patch for a little while back ( which was flawed/incomplete ).
> In the process of redoing the patch and grabbing the source from
> cvs I came
> up against this issue: what the heck tag is appropriate to use to submit
> bugfixes against for the 3.2.x version of Tomcat? I am assuming that
> tomcat_32 is the appropriate place but...
>
>
>
> ----- Original Message -----
> From: "Marc Saegesser" <marc.saegesser@apropos.com>
> To: <tomcat-dev@jakarta.apache.org>
> Sent: Friday, February 02, 2001 11:04
> Subject: RE: 3.2.2 Release?
>
>
> > One thing I don't see listed here, and is the biggest reason I
> don't think
> I
> > have the time to manage the release, is determining what bugs
> still exist
> in
> > the tomcat_32 branch and which of those, if any, should be fixed before
> > releasing 3.2.2.  This was an issue that Jon raised regarding the 3.3
> > release plan.  What is the feeling of the Tomcat development community?
> Can
> > we get away with just releasing the tip of tomcat_32 as-is or
> would such a
> > release *require* a complete review of open bugs and should the
> release be
> > held until these bugs are all addressed.
> >
> > I've been trying to make just such a review but it has been very time
> > consuming.  Maybe, since this is just a minor point release to
> an existing
> > product, we can go with what we have.
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-dev-help@jakarta.apache.org


Mime
View raw message