Re[2]:[VOTE] Tomcat 4.0.2 b2 release

[Jonathan Pierce <Jo...@seagram.com>]

Please ignore my last message, my mailer delivered the last email late to me so
I thought you were planning another release. 
Sorry

____________________Reply Separator____________________
Subject:    Re:[VOTE] Tomcat 4.0.2 b2 release
Author: "Tomcat Developers List" <to...@jakarta.apache.org>
Date:       2/22/2002 4:12 PM


Since 4.0.2 is already released, shouldn't this be tagged 4.0.3b2 ?

____________________Reply Separator____________________
Subject:    [VOTE] Tomcat 4.0.2 b2 release
Author: "Tomcat Developers List" <to...@jakarta.apache.org>
Date:       1/16/2002 3:10 PM

Hi,

I think it would be good to tag Tomcat 4.0.2 b2 at the end of the week (with
the binaries being released by monday). Here's the ballot:

<ballot>
[ ] +1 Make the release
[ ] +0 Good idea, but I can't help
[ ] -0 Bad idea
[ ] -1 No, because:



</ballot>

The release process will be the following:
- Tag j-t-c/webapp with "tomcat_402_b2"
- Update the Java sources for webapp in the main Tomcat tree to mirror the
changes; I plan to remove the duplication for the next release, and handle
webapp the same way as JK (or Coyote)
- Tag j-t-c/jk with "tomcat_402_b2" (it's fine to also tag it with something
else, I just think it's a better way to mark which version went in)
- Tag j-t-c/util with "tomcat_402_b2"
- Generate binaries for the Java code from the j-t-c components, and update
the binaries in the main Tomcat tree
- Tag the Tomcat tree with "tomcat_402_b2"
- Build and upload the main Tomcat binaries
- Build and upload the native binaries for JK and webapp
- Build and upload the RPMs

Note: IMO JK should be considered release quality in this release, and
should be enabled by default; of course, the final word on this goes to the
JK developers :)

Thanks,
Remy


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


************************************************************************
This email and any files transmitted with it are for the named person's use
only.  It may contain confidential, proprietary or legally privileged
information.  No confidentiality or privilege is waived or lost by any
mistransmission.  If you receive this message in error, please immediately
delete it and all copies of it from your system, destroy any hard copies
of it and notify the sender.  You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message if you
are not the intended recipient.

This email message has been swept by a virus software product for the
presence of computer viruses.
*************************************************************************

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


************************************************************************
This email and any files transmitted with it are for the named person's use
only.  It may contain confidential, proprietary or legally privileged
information.  No confidentiality or privilege is waived or lost by any
mistransmission.  If you receive this message in error, please immediately
delete it and all copies of it from your system, destroy any hard copies
of it and notify the sender.  You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message if you
are not the intended recipient.

This email message has been swept by a virus software product for the
presence of computer viruses.
*************************************************************************

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>