Remy Maucherat wrote:
The vote result is:
- the release plan seems to be mostly ok
- it is acceptable to use the J2SE 1.4 API for this release (only Costin
seems to disagree with that); I expect this will allow using things like
the NIO API without any difficulties or the need for compatibility
Remy Maucherat wrote:
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[ ] J2SE 5.0
/ballot
ballot
Yoav Shapira will act as the release manager for this branch:
[X] Yes
[ ] No
/ballot
Thanks :)
The vote result is:
- the release plan seems to be mostly ok
- it is acceptable to use the J2SE 1.4 API for this release (only Costin
seems to disagree with that); I expect this will allow using things like
the NIO API without any difficulties or the need for compatibility code
- Yoav will RM
Remy Maucherat schrieb:
ballot
I approve the release plan:
[x] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[x] J2SE 1.4
[ ] J2SE 5.0
/ballot
ballot
Yoav Shapira will act as the release manager for this branch:
[x] Yes
[ ] No
/ballot
Thanks :)
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[ ] J2SE 5.0
/ballot
ballot
Yoav Shapira will act as the release manager for this branch:
[X] Yes
[ ] No
/ballot
Cheers,
Amy
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[ ] J2SE 5.0
/ballot
ballot
Yoav Shapira will act as the release manager for this branch:
[X] Yes
[ ] No
/ballot
Cheers
Ian Darwin
Remy Maucherat wrote:
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[X] J2SE 5.0
/ballot
Can we support both, or do we need a new project
that will use the full Java 5 API?
Anyhow, no 1.3
Mladen Turk wrote:
Remy Maucherat wrote:
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[X] J2SE 5.0
/ballot
Can we support both, or do we need a new project
that will use the full Java 5 API?
Remy Maucherat wrote:
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[ ] J2SE 5.0
/ballot
ballot
Yoav Shapira will act as the release manager for this branch:
[X] Yes
[ ] No
/ballot
Thanks :)
Hola,
ballot
I approve the release plan:
[ X ] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[ X ] J2SE 1.4
[ ] J2SE 5.0
/ballot
ballot
Yoav Shapira will act as the release manager for this branch:
[ ] Yes
[ ] No
/ballot
I doubt I can vote
Shapira, Yoav wrote:
I doubt I can vote for/against myself, so I'll just say I'll be happy to
do the releases for a while ;)
Are you ok with releasing a first 5.5.0 build this WE or monday to
properly start this branch offically ? Or do we wait for next week ?
Rémy
Hola,
Are you ok with releasing a first 5.5.0 build this WE or monday to
properly start this branch offically ? Or do we wait for next week ?
Let's do early next week, e.g. Monday or Tuesday. I'm going to do
5.0.28 on Saturday most likely.
Yoav
This e-mail, including any attachments, is a
It looks like there are branches for 5.0 (TOMCAT_5_0) in j-t-jasper and
connectors. Is that correct? Or should both of those modules be using HEAD?
It also appears that jakarta-tomcat-site recieved tags for TOMCAT_5_0_27,
TOMCAT_5_0_26 and branch tag of TOMCAT_5_0.
-Tim
Remy Maucherat wrote:
-
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Friday, August 27, 2004 11:45 AM
To: Tomcat Developers List
Subject: Re: [VOTE] [5.5] Release plan votes
It looks like there are branches for 5.0 (TOMCAT_5_0) in j-t-jasper and
connectors. Is that correct? Or should both of those modules be using
Remy Maucherat wrote:
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[X] J2SE 5.0
/ballot
1.4 for Tomcat 5.5 is right.
For Tomcat 6, specs folks are talking about *maybe* requiring 5.0 (for
Remy Maucherat wrote:
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[ ] J2SE 5.0
/ballot
J2SE 5.0 is in beta right now, and there won't be widespread support
for it for a while, so it's
On Aug 26, 2004, at 1:13 PM, Remy Maucherat wrote:
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[ ] J2SE 5.0
/ballot
As a Tomcat user I'd appreciate it if Tomcat would support the second
newest JVM release at the time a new minor version number
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[ ] J2SE 5.0
/ballot
ballot
Yoav Shapira will act as the release manager for this branch:
[X] Yes
[ ] No
/ballot
Mark
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[ ] J2SE 1.3
[X] J2SE 1.4
[ ] J2SE 5.0
/ballot
ballot
Yoav Shapira will act as the release manager for this branch:
[X] Yes
[ ] No
/ballot
---
Outgoing mail is certified
* New native connector for Apache 2, based on mod_proxy
Is it true that it will be ready for 5.5? I thought the mod_proxy code would
be independent of tomcat version.
Otherwise ...
Remy Maucherat wrote:
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use
Remy Maucherat wrote:
ballot
I approve the release plan:
[X] Yes
[ ] No
/ballot
ballot
Tomcat 5.5 should use the following API set for the coding:
[X] J2SE 1.3
[ ] J2SE 1.4
[ ] J2SE 5.0
/ballot
Actually - use target=1.3 - but the distribution should be 1.4 based
(i.e. no Xerces ).
I'm also ok
21 matches
Mail list logo