tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: [VOTE] Make released versions RTC
Date Wed, 12 Sep 2007 12:27:54 GMT
Jim Jagielski wrote:
> On Sep 10, 2007, at 4:47 PM, Remy Maucherat wrote:
>> The main idea is that since there's only one trunk branch, there
>> should be agreement on APIs and important topics to proceed
> ++1. So let's start that now. Since there is not agreement on APIs,
> how do we proceed from here? Or, in other words, how do achieve
> agreement on APIs?

Mostly we are talking about new APIs for new features that, once
agreed, can be added to the current version.

It is changes to existing APIs that are more problematic. The current
APIs will need to change occasionally (eg the Geronimo changes) and
will need to be a new point version (6.1, 6.5 - whatever).

We are already managing:
- 4.1.x (mainly security and the odd bug)
- 5.0.x (security only but needs some header work before release)
- 5.5.x (security, bugs, some back porting of features)
- 6.0.x (security, bugs & new features)

Maintaining, to various degrees, 4 branches is already a fair amount
of work for the team. I don't want to see more maintained branches
than absolutely necessary.

What this means is we need a set of agreed API changes for 6.0.x that
will eventually become 6.1.x/6.5.x. I see as
the way to get this agreement.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message