tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <wbar...@wilshire.com>
Subject Re: [VOTE] Release Plan for Tomcat 3.3 (final release)
Date Mon, 10 Sep 2001 23:27:59 GMT
A long release cycle, but a short beta (and a lot of people don't download
until beta).  Of course I agree that 3.3 is a great improvement on 3.2 (even
as far back as M2 when I first started using it).  Granted, all of the bugs
that I know of in B2 have been fixed, but I've only had it up for about a
week to bang on it.  Mostly it's just my frustration that I'd like to be
involved (at least with testing), but as a part-timer on tomcat-dev I
probably won't be able to with the proposed release calendar.

----- Original Message -----
From: <cmanolache@yahoo.com>
To: <tomcat-dev@jakarta.apache.org>
Sent: Monday, September 10, 2001 4:20 PM
Subject: Re: [VOTE] Release Plan for Tomcat 3.3 (final release)


> On Mon, 10 Sep 2001, William Barker wrote:
>
> > For what it's worth (since I can't vote), I agree with Jon.  TC3.3
hasn't
> > had a long enough beta cycle yet to push through an RC cycle this fast.
As
> > it is, I'm going to be lucky to have time to install RC1 before RC2
comes
> > out.  Keeping up with 4.0 isn't a good enough reason, since I'm sure
that
> > there are plenty of people like me who can't even think of moving to 4.0
> > until it has release-quality connectors.
>
> In the last 3-4 months all we did was fix bugs and improve usability.
> There are countless bugs from 3.2 that were fixed in 3.3, many small
> things that were tuned, etc - and I'm pretty confident the current code is
> ready ( and significantly better that 3.2 ).
>
> I don't know what 'long enough' means, my impression is that we had a
> far too long release cycle for 3.3 already.
>
> Of course, if any major bug shows up - we'll postpone the release as much
> as it's needed to fix it.
>
> Costin
>
>
>
>
> > ----- Original Message -----
> > From: "Jon Stevens" <jon@latchkey.com>
> > To: "tomcat-dev" <tomcat-dev@jakarta.apache.org>
> > Sent: Monday, September 10, 2001 12:38 PM
> > Subject: Re: [VOTE] Release Plan for Tomcat 3.3 (final release)
> >
> >
> > > on 9/10/01 9:12 AM, "Christopher Cain" <ccain@mhsoftware.com> wrote:
> > >
> > > >
> > > >> ===== Tomcat 3.3 Final Release Plan Ballot =====
> > > >> [ ] +1    I am in favor of this plan, and will help
> > > >> [ ] +0    I am in favor of this plan, but am unable to help
> > > >> [ ] -0    I not in favor of this plan
> > > >> [X] -1    I am opposed to this plan, and my reason(s) are:
> > > >> ================================================
> > >
> > >
> >
<http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASS
> > >
> >
IGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&e
> > >
> >
mail2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&chang
> > >
> >
edin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Tomcat+3&short
> > >
> >
_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_fil
> > >
> >
e_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&field0-0
> >
> -0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+
> > sa
> > > me+sort+as+last+time>
> > >
> > > Essentially a query for all new/assigned/reopened bugs in Tomcat 3.
> > >
> > > Is there also a recursive test to make sure that all 3.2.x
reported/fixed
> > > bugs are also fixed in 3.3?
> > >
> > > -jon
> > >
> > >
> >
> >
> > *----*
> >
> > This message is intended only for the use of the person(s) listed above
> > as the intended recipient(s), and may contain information that is
> > PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient,
> > you may not read, copy, or distribute this message or any attachment.
> > If you received this communication in error, please notify us
immediately
> > by e-mail and then delete all copies of this message and any
attachments.
> >
> >
> > In addition you should be aware that ordinary (unencrypted) e-mail sent
> > through the Internet is not secure. Do not send confidential or
sensitive
> > information, such as social security numbers, account numbers, personal
> > identification numbers and passwords, to us via ordinary (unencrypted)
> > e-mail.
> >
>
>


*----*

This message is intended only for the use of the person(s) listed above 
as the intended recipient(s), and may contain information that is 
PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, 
you may not read, copy, or distribute this message or any attachment.  
If you received this communication in error, please notify us immediately 
by e-mail and then delete all copies of this message and any attachments.


In addition you should be aware that ordinary (unencrypted) e-mail sent 
through the Internet is not secure. Do not send confidential or sensitive 
information, such as social security numbers, account numbers, personal 
identification numbers and passwords, to us via ordinary (unencrypted) 
e-mail. 

Mime
View raw message