on 9/10/01 2:13 PM, "Pier Fumagalli" <[EMAIL PROTECTED]> wrote:
> 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).
The fact that it is ready to go should be recorded in the issue tracking
system by marking the issues as VERIFIED/CLOSED.
> Too late, we are already progressing with RCs as planned, so, next time,
> vote in a timely manner :) :) :)
I don't care about the RC's. I care about a T4.0 FINAL.
If T4.0 FINAL has bugs not in VERIFIED/CLOSED state, then I'm going to vote
-1 on its release. However, of course, I believe that there is a majority
vote in that case, so I will probably be overruled.
> 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).
I'm really afraid that T4.0 FINAL is going to get really bad reviews as a
result of this. I sure hope that connector is rock solid (like Jserv's is)
on release day.
-jon
