It works for me, and if it just involves swapping 3.2 and 3.3 I don't see a
problem (or, at least you'll win the vote).  Personally I wouldn't try to
move the 4.0 without first posting a [VOTE] (although since you're moving it
up, it will likely win).
----- Original Message -----
From: "Bojan Smojver" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Sunday, November 18, 2001 8:28 PM
Subject: Re: cvs commit: jakarta-tomcat-site/xdocs index.xml


> Thanks. Didn't actually pay attention to that part. Fixing now...
>
> BTW, do you think it would be better if the order of described releases
> is changed? In other words, Tomcat 3.3/4.0 first and then others.
>
> Bojan
>
> Bill Barker wrote:
> >
> > You forgot to remove the "is in beta testing" from the 3.3 description.
> > ----- Original Message -----
> > From: <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Sunday, November 18, 2001 5:49 PM
> > Subject: cvs commit: jakarta-tomcat-site/xdocs index.xml
> >
> > > bojan       01/11/18 17:49:33
> > >
> > >   Modified:    xdocs    index.xml
> > >   Log:
> > >   Present TC 3.3 as production quality release of the 3.x series
> > >
> > >   Revision  Changes    Path
> > >   1.12      +22 -10    jakarta-tomcat-site/xdocs/index.xml
> > >
> > >   Index: index.xml
> > >   ===================================================================
> > >   RCS file: /home/cvs/jakarta-tomcat-site/xdocs/index.xml,v
> > >   retrieving revision 1.11
> > >   retrieving revision 1.12
> > >   diff -u -r1.11 -r1.12
> > >   --- index.xml 2001/10/22 16:14:42 1.11
> > >   +++ index.xml 2001/11/19 01:49:33 1.12
> > >   @@ -28,18 +28,30 @@
> > >    </section>
> > >
> > >    <section name="Tomcat Versions">
> > >   -<p>There are several versions of Tomcat currently available for
> > download.  Version 3.1.1
> > >   -is a legacy release.  Version 3.2.3 is the current production
quality
> > release
> > >   -for the Servlet 2.2 and JSP 1.1 specifications.  Tomcat 3.3
> > >   -is the latest continuation of the Tomcat 3.x architecture.  All
Tomcat
> > 3.x releases
> > >   -trace their heritage back to the original Servlet and JSP
> > implementations that Sun
> > >   -donated to the Apache Software Foundation.  The 3.x versions all
> > implement the
> > >   -Servlet 2.2 and JSP 1.1 specifications.
> > >   +<p>There are several versions of <strong>Tomcat 3.x</strong>
currently
> > >   +available for download:</p>
> > >   +
> > >   +<ul>
> > >   +<li>Version 3.3 is the current production quality release for the
> > Servlet 2.2
> > >   +and JSP 1.1 specifications.  Tomcat 3.3 is the latest continuation
of
> > the
> > >   +Tomcat 3.x architecture and it is more advanced then 3.2.3, which
is
> > the 'old'
> > >   +production quality release.</li>
> > >   +<li>Version 3.2.3 is the 'old' production quality release and is
now in
> > >   +maintenance only mode.</li>
> > >   +<li>Version 3.1.1 is a legacy release.</li>
> > >   +</ul>
> > >   +
> > >   +<p>
> > >   +All Tomcat 3.x releases trace their heritage back to the original
> > Servlet and
> > >   +JSP implementations that Sun donated to the Apache Software
Foundation.
> > The
> > >   +3.x versions all implement the <strong>Servlet 2.2</strong> and
> > <strong>JSP
> > >   +1.1</strong> specifications.
> > >    </p>
> > >
> > >   -<p>Tomcat 4.0 implements a new servlet container ( called Catalina)
> > that
> > >   -is based on completely new architecture.  The 4.0 release
implements
> > >   -the Servlet 2.3 and JSP 1.2 specifications.  </p>
> > >   +<p><strong>Tomcat 4.0</strong> implements a new servlet container
> > (called
> > >   +Catalina) that is based on completely new architecture.  The 4.0
> > release
> > >   +implements the <strong>Servlet 2.3</strong> and <strong>JSP
> > 1.2</strong>
> > >   +specifications.  </p>
> > >
> > >    <p>The releases are described in more detail below to help you
> > determine
> > >    which one is right for you.  More details about each release can be
> > found in
> > >
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > >
> >
> > *----*
> >
> > 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.
> >
> > --
> > To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>


*----*

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. 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to