Re: JK2 2.0.0 Release proposal

2002-09-24 Thread Henri Gomez

Mladen Turk wrote:
 Hi,
 
 Since there is no major showstoppers and
 a) The vhosts should work now
 b) Socket BUG 12346 is solved
 
 Here is the release plan:
 
 1. 09/25/2002  - Freeze the further development.
 
 2. 09/26/2002  - If there is no major bugs tag the release as JK2_2_0_0
 
 3. 09/26/2002  - Prepare the source release (zip and tar.gz)
   Start building binaries (What platforms?)

+1

 Platform WIN32 (I can do that):
   mod_jk2/Apache2.0.40 (or 2.0.42 if released).
   mod_jk2/Apache1.3.26/APRAPR_UTIL from 2.0.40
   i_r2.dll/APRAPR-UTIL from 2.0.40

 Any one wish to make binaries for other platforms?

Linux i386 and may be cygwin also

 4. 09/27/2002 - Should be all over at
 http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v
 2.0.0/
 
 Comments and thoughts?

Let's go, JK 1.2.0 should be out tomorrow




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




Re: JK2 2.0.0 Release proposal

2002-09-24 Thread Costin Manolache

+1 and thanks for steping up :-)

Mladen Turk wrote:

 Hi,
 
 Since there is no major showstoppers and
 a) The vhosts should work now
 b) Socket BUG 12346 is solved
 
 Here is the release plan:
 
 1. 09/25/2002  - Freeze the further development.
 
 2. 09/26/2002  - If there is no major bugs tag the release as JK2_2_0_0

Let's call this a 'milestone' or 'build', as is done in 4.x and apache.

 
 3. 09/26/2002  - Prepare the source release (zip and tar.gz)
 Start building binaries (What platforms?)
 
 Platform WIN32 (I can do that):
 mod_jk2/Apache2.0.40 (or 2.0.42 if released).
 mod_jk2/Apache1.3.26/APRAPR_UTIL from 2.0.40
 i_r2.dll/APRAPR-UTIL from 2.0.40
 
 Any one wish to make binaries for other platforms?
 
 4. 09/27/2002 - Should be all over at
 http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v
 2.0.0/

Then have a vote on the 'label' - I personally prefer to call it 
'beta', not release. 

I'm very happy with the stability of the code, but for 4.1 I would like
to have jk1.2 considered the 'stable' connector and jk2.0 at beta level.
That reflects the big difference in testing and use they had so far.

After 1.2 is released and 2.0 is beta, we should froze 1.2 tree and 
start doing all work in 2.0, and eventually have 2.0 released shortly
after.

BTW, there are several features in 2.0 I wouldn't consider 'release quality'
yet - the shmem, unix channel, even jni had only little testing so
far ( compared with the very large amount of use jk1.2 had )

Costin

 
 Comments and thoughts?
 
 MT.

-- 
Costin



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




RE: JK2 2.0.0 Release proposal

2002-09-24 Thread Mladen Turk

Contin wrote:
 
 Let's call this a 'milestone' or 'build', as is done in 4.x 
 and apache.
 

So JK2_0_BETA as tag name and jk2.0-beta as build name, but
I would reather prefer only numbers an just said OK jk-2.0.0 is Beta
version.


MT.


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




RE: JK2 2.0.0 Release proposal

2002-09-24 Thread Ignacio J. Ortega

 De: Mladen Turk [mailto:[EMAIL PROTECTED]]
 Enviado el: 24 de septiembre de 2002 13:28
 
 
 Hi,
 
 Since there is no major showstoppers and
 a) The vhosts should work now
 b) Socket BUG 12346 is solved
 

Thanks for volunteer, and thanks for the fixes..

 Here is the release plan:
 

+1 for the overall plan, but what if we use for jk2 the same strategy
than tomcat 4.1?


Saludos ,
Ignacio J. Ortega


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




RE: JK2 2.0.0 Release proposal

2002-09-24 Thread Costin Manolache

Mladen Turk wrote:

 Contin wrote:
 
 Let's call this a 'milestone' or 'build', as is done in 4.x
 and apache.
 
 
 So JK2_0_BETA as tag name and jk2.0-beta as build name, but
 I would reather prefer only numbers an just said OK jk-2.0.0 is Beta
 version.

I think the way it works ( for 4.0 and apache ) is:
- 2.0.x as 'build number' 
- a proposal on tomcat-dev to release the build with a certain
label ( beta in this case )

The labels will use the build number, the announce will use the label.


 
 
 MT.

-- 
Costin



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