tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: CVS branching
Date Tue, 01 Jun 2004 20:04:51 GMT

Hi,
I'd like to get Gump to build.  It seems like it's getting the wrong
struts version (1.0.2 instead of 1.1), thereby causing compile errors
for the admin webapp?  Anyways, let's not continue that discussion in
this thread.

Yoav Shapira
Millennium Research Informatics


>-----Original Message-----
>From: Bill Barker [mailto:wbarker@wilshire.com]
>Sent: Tuesday, June 01, 2004 1:35 PM
>To: Tomcat Developers List
>Subject: Re: CVS branching
>
>Since Gump(y) hasn't built for months, it can't complain more than it
>already is doing ;-).
>
>The real question is whether we want to run Gump on the 5.0 branch as
well
>as HEAD.
>
>----- Original Message -----
>From: "Shapira, Yoav" <Yoav.Shapira@mpi.com>
>To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
>Sent: Tuesday, June 01, 2004 6:00 AM
>Subject: CVS branching
>
>
>
>Hi,
>So at some point soon (the next day or two), we want to put the current
>tomcat 5 code on a branch called tomcat_5_0 (the actual branch name is
>tentative but let's use tomcat_5_0 for example).  We'll do this after
>tagging TOMCAT_5_0_26 on the main branch.
>
>The actual CVS command is easy:
>cvs rtag -r TOMCAT_5_0_26 -b TOMCAT_5_0
>(repeat once for each tomcat CVS module, jakarta-tomcat-5,
>jakarta-tomcat-catalina, etc.)
>
>Subsequent checkouts and tagging operations against this have to
specify
>-r TOMCAT_5_0 or else they work against the default, main/head branch.
>Commits are easy (don't need a branch specified) as they automatically
>work against the branch where the checkout was done.
>
>Is that it?  Should we be concerned about the fact that the main/head
>codebase will not be as stable, so users trying to build head (or
>automated/nightly/gump trying to build head) may run into trouble?
>
>Yoav Shapira
>Millennium Research Informatics
>
>
>
>
>
>This e-mail, including any attachments, is a confidential business
>communication, and may contain information that is confidential,
>proprietary
>and/or privileged.  This e-mail is intended only for the individual(s)
to
>whom it is addressed, and may not be saved, copied, printed, disclosed
or
>used by anyone else.  If you are not the(an) intended recipient, please
>immediately delete this e-mail from your computer system and notify the
>sender.  Thank you.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>




This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message