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
"Tomcat 3.x". The only purpose is to identify an ongiong development process
for 4.x as we move fowards, and follows standard release management practices.
What we need to do, along with a feature freeze on 4.0 in order to enter beta,
is to not stifle further 4.x development (such as whatever comes of the current
discussions about distributed session management support).In order to avoid
destabilizing a 4.0 release, we clearly do not want to do changes on such a
fundamental feature during beta. So, we're going to need to temporarily have
two parallel development streams in 4.x.
Given that we're using CVS, there are two basic choices -- a branch in the
"jakarta-tomcat-4.0" repository, or a separate repository. Having seen the
problems that branches can cause, and seeing what other projects (like the
Apache web server itself) do, it makes more sense to me to do the latter.
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 this is identical
for a branch or for a separate repository.
Bottom Line -- it does not appear to me that "too many branches" (without a
suggested alternative) is a valid
reason for a veto. If you have an alternative suggestion for how we should
organize 4.x ongoing release management, I'm all ears.
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
