"Jon Stevens" <[EMAIL PROTECTED]> wrote:
> on 9/10/01 1:14 PM, "Pier Fumagalli" <[EMAIL PROTECTED]> wrote:
> 
>> To be fair, I see only 12 bugs with Tomcat 3.x, and ONLY ONE on 3.3
> 
> I'm also worried about regression testing.

Well, let them do their fucking job... If we gave them committer access, it
means that we trust them. If they say that 3.3 is ready to go, well, I'm not
going to stop them because FIRST I never contributed a line of code, SECOND
I gave THEM responsibility when I voted, or not vetoed their committer
status, THIRD I never tried out 3.3, so don't know what's the status of bugs
is, but (see two) I trust them (or I have to).

>> , whereas
>> there are 26 on Tomcat 4.0 currently open, and you didn't vote -1 on 4.0's
>> release plan... I'm not trying to "help out" anyone, neither trying to say
>> that 4.0 should be given a -1, but I'm just trying to say that being fair,
>> you can't veto their release given the reasons you listed above...
> 
> I haven't voted for 4.0's release plan yet.

Yeah, noticed...

> However, given what you just said, -1 on that as well.

Too late, we are already progressing with RCs as planned, so, next time,
vote in a timely manner :) :) :)

>> As I said, despite our disagreements and this whole "war" between 3.3 and
>> 4.0, I want to see a production quality R.I. for Servlet 2.2 and JSP 1.1,
>> and even if technically me and the 3.3 team are not "on the same line of
>> thoughts", I believe that if they proposed a release plan to get out final
>> they know what they're doing...
> 
> If there are bugs in the till, they should get resolved first.

That's why the WebApp module is not yet out with RC1 (the java part is
tagged and not-modifiable, but there are still some issues in C I want to
fix before tagging).

    Pier

Reply via email to