Bob Jamison wrote:
> Hi, all,
>
> Will 4.1 be read-visible in the "cvspublic" repository?
>
Ooops ... forgot a couple steps. The two new repositories ("jakarta-tomcat-4.1" and
"jakarta-servletapi-4") are now visible to anonymous CVS. Web site updates are
forthcoming.
>
> Bob Jamison
> LinCom
Craig R. McClanahan wrote:
>
>
> (2) Tomcat 4.1 Repository
>
> As we approach a release quality build for Tomcat 4.0, it is also time to split
> the development of major new functionality (such as the distributed session
> management currently under discussion) into a development process that
Jon Stevens wrote:
> When you do a cvs co jakarta-tomcat-4.0, then you will get
> a directory on your hard disk with 4.0. If you then want
> to check out 4.1, you need to first reaname
> jakarta-tomcat-4.0 to something else, then checkout 4.1
> on the branch, then rename it to something else, the
On 1/3/01 4:13 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]>
wrote:
> * Branches tend to be less visible to project newcomers --
> for example, anyone who checks out the main branch of
> "jakarta-tomcat" today is going to wonder why it is quite
> different from the 3.2.1 source distribution that
On 1/3/01 4:02 PM, "Jon Stevens" <[EMAIL PROTECTED]> wrote:
> When you do a cvs co jakarta-tomcat-4.0, then you will get a directory on
> your hard disk with 4.0. If you then want to check out 4.1, you need to
> first reaname jakarta-tomcat-4.0 to something else, then checkout 4.1 on the
> branch
on 1/5/2001 6:51 AM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote:
> Tomcat has the same problem as Struts and most Open Source
> projects (it is not just an Apache thing):
> * NOT ENOUGH DOCUMENTATION *
Sigh, this is a lame request now. We could write documentation until we are
blue in the face and
.
> -Original Message-
> From: Kief Morris [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 05, 2001 9:43 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [VOTES] Tomcat 4.0-Beta-1 and New CVS Repositories
>
>
> Marc Saegesser typed the following on 08:12 AM 1/5/2001 -0600
> >I
Marc Saegesser typed the following on 08:12 AM 1/5/2001 -0600
>I don't see the need for branch until Tomcat 4.0 Final is relased. Until
>then, from a source control perspective, a beta release is no different than
>a milestone release. In short, what code would ever be checked into "main"
>that w
Tomcat has the same problem as Struts and most Open Source
projects (it is not just an Apache thing):
* NOT ENOUGH DOCUMENTATION *
In the case of the Jakarta projects the APIs documentation is
usually quite satisfactory but the Introductions, HOW-TOs,
User Guides, Architecture and other overv
> (1) Tomcat 4.0 Beta 1
-0.
I don't see the need for branch until Tomcat 4.0 Final is relased. Until
then, from a source control perspective, a beta release is no different than
a milestone release. In short, what code would ever be checked into "main"
that would not also belong on the branch?
>I don't see any problem - there are 2 codebases - the
>"original" tomcat (
>3.x ) and catalina ( 4.x ).
You're in the project but imagine when a new user arrive and
want to use a servlet engine ;-) The question will be must
I use 3.2, 3.3, 4.0 or 4.1 ?-)
A simple help rule could be :
- If yo
"Craig R. McClanahan" wrote:
>
> Now that we've all recovered from New Years (and watched Oregon State teach
> Notre Dame a few things about football -- go Beavers! :-), it's time to lay out
> the next steps in Tomcat 4.0's lifetime. Here's what I propose:
>
> (1) Tomcat 4.0 Beta 1
> [...] prop
> >so +1 , but i continue to not see any advantages in maintain another
> >repository..
> >
>
> Like Nacho I turn my -1 to +1 since I don't want the TC 4.x development
> to be stopped or features freezed but I feel that It will became
> hard to find our way in 3.2, 3.3, 4.0 and 4.1
I don't see a
>so +1 , but i continue to not see any advantages in maintain another
>repository..
>
Like Nacho I turn my -1 to +1 since I don't want the TC 4.x development
to be stopped or features freezed but I feel that It will became
hard to find our way in 3.2, 3.3, 4.0 and 4.1
---
nahan [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 04, 2001 11:34 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [VOTES] Tomcat 4.0-Beta-1 and New CVS Repositories
>
>
> Marc Saegesser wrote:
>
> > > -Original Message-
> > > From: Craig R. McClanahan [
Marc Saegesser wrote:
> > -Original Message-
> > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> >
> > (1) Tomcat 4.0 Beta 1
> >
> > The existing "jakarta-tomcat-4.0" repository will be branched with label
> > "tomcat_40_branch", and each 4.0.x beta and release will receive
> > a l
> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
>
> (1) Tomcat 4.0 Beta 1
>
> The existing "jakarta-tomcat-4.0" repository will be branched with label
> "tomcat_40_branch", and each 4.0.x beta and release will receive
> a label such as
> "tomcat_40_b1". The "ma
GOMEZ Henri wrote:
>
> -1 - We'll have now 3.2, 3.3, 4.0 and 4.1 branches
> Too many branches for the same project.
> Please don't reopen a 3.x against 4.x campaign.
Henri, I would like to ask you to voluntarily remove your -1. The only way
to make progress towards a 4.0 release is to sl
Glenn Nielsen wrote:
>
> "Craig R. McClanahan" wrote:
> >
> > Now that we've all recovered from New Years (and watched Oregon State teach
> > Notre Dame a few things about football -- go Beavers! :-), it's time to lay out
> > the next steps in Tomcat 4.0's lifetime. Here's what I propose:
> >
>
Dan Milstein wrote:
> >
> > On the other hand, a separate repository causes no problems that I've
> > experienced, and avoids all of the issues listed above.
>
> I agree that branches under CVS are way, way confusing, and so I'll support a
>separate repository. The one disadvantage I do see, ho
>
> On the other hand, a separate repository causes no problems that I've
> experienced, and avoids all of the issues listed above.
I agree that branches under CVS are way, way confusing, and so I'll support a separate
repository. The one disadvantage I do see, however, is that we'll lose the
Hola Jon:
> The problem is that say you are working on 4.0 and 4.1 at the
> same time.
>
I do this with branches ( cocoon2 , 3.2 , 3.X ) all the time, only by
using another directory..
> When you do a cvs co jakarta-tomcat-4.0, then you will get a
> directory on
> your hard disk with 4.0. If
Nacho wrote:
> > (1) Tomcat 4.0 Beta 1
> >
>
> +1
>
> >
> > (2) Tomcat 4.1 Repository
> >
> >
>
> -1
>
> Please explain what are the problem with branches, i dont see why label
> a branch with tomcat_40 and do 4.1 development in head branch is bad, i
> dont see any desestabilization or such in th
Hola a TOdos:
> > (2) Tomcat 4.1 Repository
> >
> >
>
I've changed my opinion, it's the same
so +1 , but i continue to not see any advantages in maintain another
repository..
Saludos ,
Ignacio J. Ortega
-
To unsubscribe
on 1/3/2001 3:55 PM, "Nacho" <[EMAIL PROTECTED]> wrote:
> Please explain what are the problem with branches, i dont see why label
> a branch with tomcat_40 and do 4.1 development in head branch is bad, i
> dont see any desestabilization or such in this way of doing things, i
> want to know why is
> (1) Tomcat 4.0 Beta 1
>
+1
>
> (2) Tomcat 4.1 Repository
>
>
-1
Please explain what are the problem with branches, i dont see why label
a branch with tomcat_40 and do 4.1 development in head branch is bad, i
dont see any desestabilization or such in this way of doing things, i
want to k
on 1/3/2001 1:48 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]>
wrote:
> NOTE: There will be a short period of time where "double posting" of bug fix
> patches will be required (which will end when we stop doing 4.0.x maintenance
> releases because 4.1.x is stable). The developer effort to do th
GOMEZ Henri wrote:
>
> >(2) Tomcat 4.1 Repository
>
> -1 - We'll have now 3.2, 3.3, 4.0 and 4.1 branches
> Too many branches for the same project.
> Please don't reopen a 3.x against 4.x campaign.
>
I'm not ... nothing in the proposal says anything at all about anything labelled
"Tom
Glenn Nielsen wrote:
> "Craig R. McClanahan" wrote:
>
> > The existing "jakarta-tomcat-4.0" repository will be branched with label
> > "tomcat_40_branch", and each 4.0.x beta and release will receive a label such as
> > "tomcat_40_b1". The "main" branch of this repository will be active for bug
>(1) Tomcat 4.0 Beta 1
+1 - Need to enter Beta process
>(2) Tomcat 4.1 Repository
-1 - We'll have now 3.2, 3.3, 4.0 and 4.1 branches
Too many branches for the same project.
Please don't reopen a 3.x against 4.x campaign.
>(3) New "jakarta-servletapi-4.0" CVS Repository
+1
---
"Craig R. McClanahan" wrote:
>
> Now that we've all recovered from New Years (and watched Oregon State teach
> Notre Dame a few things about football -- go Beavers! :-), it's time to lay out
> the next steps in Tomcat 4.0's lifetime. Here's what I propose:
>
> (1) Tomcat 4.0 Beta 1
>
> The cod
> (1) Tomcat 4.0 Beta 1
+1
> (2) Tomcat 4.1 Repository
+1
> (3) New "jakarta-servletapi-4.0" CVS Repository
+1
-- Pierre
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
> Now that we've all recovered from New Years (and watched Oregon State
teach
> Notre Dame a few things about football -- go Beavers! :-), it's time to
lay out
> the next steps in Tomcat 4.0's lifetime. Here's what I propose:
>
>
>
> (1) Tomcat 4.0 Beta 1
>
> The code for Tomcat 4.0 has proven to
33 matches
Mail list logo
