Re: jk2 2.0.4 release plan
[EMAIL PROTECTED] a écrit : -Original Message- From: Henri Gomez [mailto:[EMAIL PROTECTED] Subject: jk2 2.0.4 release plan Comments welcome I can throw some tests at the build given some notice if that is any help. Thanks for picking this up. Thanks, we're working with JFC to clean the build :-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jk2 2.0.4 release plan
-Original Message- From: Henri Gomez [mailto:[EMAIL PROTECTED] Subject: jk2 2.0.4 release plan Comments welcome I can throw some tests at the build given some notice if that is any help. Thanks for picking this up. Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Jess Holle a écrit : Dave Oxley wrote: Henri, What is the current state of JK2. Is it alpha, beta or GA. If this is going to be an alpha release, what is the plan for a GA release. I would like to migrate from JK when it is stable. This is a *very* good question. Last time I dared to ask the consensus was mod_jk was a better idea for a production system -- but there was a good deal of dissent on this question... Well it's really a good question. GA level should be qualified by users, and more users, more bugs reports and more experience. BTW, we should make this release, to have such return from users. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Henri Gomez [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Mike Anderson a écrit : I'll be happy to deliver zips instead of NLMS. for NetWare. Henri (and others) since we are tagging and releasing jk2 can/should we do the same for jk since I know there is added functionality (Ping/Pong and timeouts) there as well? Well, one release at a time, users urge us for jk2 release, jk release could wait some time (Bill ?) Yeah, well, I suppose that now that I'm an all-great-and-powerful PMC member, I could RM a JK release. However, I'd like to get out a TC 3.3.2 before that (so, if anyone else wants to RM JK in the meantime, you've got my +1 :). Also, if Larry wants to jump in to RM 3.3.2, I'll step aside, since he has done such a great job on all of the other 3.3 releases. The rules for 3.3 releases are still old-school. I'll try to get a [PROPOSAL] together by the end of the week. If that's not rejected, then we go to a [VOTE] (which will give me time to clarify if I count PMC members or committers as binding votes). In the unlikely event that we get enough people to care about 3.3 enough to vote (seeing the trouble that Remy has getting people to vote :), then there will be a 3.3.2 release. As cool as it would be to have a 3.3.3 release, I'd probably consider the 3.3.2 release to be an EOL release for the 3.x line. Security releases would still be provided, but not much more. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Bill Barker a écrit : Henri Gomez [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Mike Anderson a écrit : I'll be happy to deliver zips instead of NLMS. for NetWare. Henri (and others) since we are tagging and releasing jk2 can/should we do the same for jk since I know there is added functionality (Ping/Pong and timeouts) there as well? Well, one release at a time, users urge us for jk2 release, jk release could wait some time (Bill ?) Yeah, well, I suppose that now that I'm an all-great-and-powerful PMC member, I could RM a JK release. However, I'd like to get out a TC 3.3.2 before that (so, if anyone else wants to RM JK in the meantime, you've got my +1 :). Also, if Larry wants to jump in to RM 3.3.2, I'll step aside, since he has done such a great job on all of the other 3.3 releases. The rules for 3.3 releases are still old-school. I'll try to get a [PROPOSAL] together by the end of the week. If that's not rejected, then we go to a [VOTE] (which will give me time to clarify if I count PMC members or committers as binding votes). In the unlikely event that we get enough people to care about 3.3 enough to vote (seeing the trouble that Remy has getting people to vote :), then there will be a 3.3.2 release. As cool as it would be to have a 3.3.3 release, I'd probably consider the 3.3.2 release to be an EOL release for the 3.x line. Security releases would still be provided, but not much more. +100 for 3.3.2 release, I'm waiting for about ... months :) If you work on it, I could get jk2 RM job :-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[OT] TEST Re: jk2 2.0.4 release plan
Test At 01:56 AM 2/4/2004, you wrote: Bill Barker a écrit : Henri Gomez [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Mike Anderson a écrit : I'll be happy to deliver zips instead of NLMS. for NetWare. Henri (and others) since we are tagging and releasing jk2 can/should we do the same for jk since I know there is added functionality (Ping/Pong and timeouts) there as well? Well, one release at a time, users urge us for jk2 release, jk release could wait some time (Bill ?) Yeah, well, I suppose that now that I'm an all-great-and-powerful PMC member, I could RM a JK release. However, I'd like to get out a TC 3.3.2 before that (so, if anyone else wants to RM JK in the meantime, you've got my +1 :). Also, if Larry wants to jump in to RM 3.3.2, I'll step aside, since he has done such a great job on all of the other 3.3 releases. The rules for 3.3 releases are still old-school. I'll try to get a [PROPOSAL] together by the end of the week. If that's not rejected, then we go to a [VOTE] (which will give me time to clarify if I count PMC members or committers as binding votes). In the unlikely event that we get enough people to care about 3.3 enough to vote (seeing the trouble that Remy has getting people to vote :), then there will be a 3.3.2 release. As cool as it would be to have a 3.3.3 release, I'd probably consider the 3.3.2 release to be an EOL release for the 3.x line. Security releases would still be provided, but not much more. +100 for 3.3.2 release, I'm waiting for about ... months :) If you work on it, I could get jk2 RM job :-) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Bill Barker wrote: Henri Gomez [EMAIL PROTECTED] wrote in message Yeah, well, I suppose that now that I'm an all-great-and-powerful PMC member, I could RM a JK release. However, I'd like to get out a TC 3.3.2 before that (so, if anyone else wants to RM JK in the meantime, you've got my +1 :). Also, if Larry wants to jump in to RM 3.3.2, I'll step aside, since he has done such a great job on all of the other 3.3 releases. The rules for 3.3 releases are still old-school. I'll try to get a [PROPOSAL] together by the end of the week. If that's not rejected, then we go to a [VOTE] (which will give me time to clarify if I count PMC members or committers as binding votes). In the unlikely event that we get enough people to care about 3.3 enough to vote (seeing the trouble that Remy has getting people to vote :), then there will be a 3.3.2 release. As cool as it would be to have a 3.3.3 release, I'd probably consider the 3.3.2 release to be an EOL release for the 3.x line. Security releases would still be provided, but not much more. +1 :) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Bill Barker wrote: committers as binding votes). In the unlikely event that we get enough people to care about 3.3 enough to vote (seeing the trouble that Remy has getting people to vote :) You're torturing me. I thinnk you should be able to get enough +1s, though (you, Henri, JF, Larry; that's four already). I have two +1s so far for 4.1.30 after one week, so the build seems to be on its way to the trash ;) Not that it's bad, there's probably not been enough testing to warrant the Stable stamp. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Remy Maucherat a écrit : Bill Barker wrote: committers as binding votes). In the unlikely event that we get enough people to care about 3.3 enough to vote (seeing the trouble that Remy has getting people to vote :) You're torturing me. I thinnk you should be able to get enough +1s, though (you, Henri, JF, Larry; that's four already). And may be Costin also :) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jk2 2.0.4 release plan
Hi Bill, Thanks for all your help with Tomcat 3.3.x. A proposal would be a good start towards a Tomcat 3.3.2 release. I'm taking it as a given that there is sufficient interest for at least one more 3.3 release. If the proposal includes switch from the old style release to Tomcat 4/5's new style, I would be +1 for that. I am willing to work with you towards a release with either you or me as the RM. I can promise, at minimum, to run the build scripts I have that produce the set of binary and source distribution files that I have used in the past. I could also sign them with my PGP key and try to determine if I need any additional karma to publish the files, which has changed a bit since the last release. As for remaining work on 3.3.2, the only things that pop into my head at the moment is updating the 3.3 coyote connector to deal with the new character encoding behavior and addressing JTC-util's use of J2SE 1.4. I may be able to look at the coyote connector updates this week end. Hopefully together we can end Henri's wait for the next 3.3.x release. :) Cheers, Larry -Original Message- From: Bill Barker [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 5:02 AM To: [EMAIL PROTECTED] Subject: Re: jk2 2.0.4 release plan Henri Gomez [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Mike Anderson a écrit : I'll be happy to deliver zips instead of NLMS. for NetWare. Henri (and others) since we are tagging and releasing jk2 can/should we do the same for jk since I know there is added functionality (Ping/Pong and timeouts) there as well? Well, one release at a time, users urge us for jk2 release, jk release could wait some time (Bill ?) Yeah, well, I suppose that now that I'm an all-great-and-powerful PMC member, I could RM a JK release. However, I'd like to get out a TC 3.3.2 before that (so, if anyone else wants to RM JK in the meantime, you've got my +1 :). Also, if Larry wants to jump in to RM 3.3.2, I'll step aside, since he has done such a great job on all of the other 3.3 releases. The rules for 3.3 releases are still old-school. I'll try to get a [PROPOSAL] together by the end of the week. If that's not rejected, then we go to a [VOTE] (which will give me time to clarify if I count PMC members or committers as binding votes). In the unlikely event that we get enough people to care about 3.3 enough to vote (seeing the trouble that Remy has getting people to vote :), then there will be a 3.3.2 release. As cool as it would be to have a 3.3.3 release, I'd probably consider the 3.3.2 release to be an EOL release for the 3.x line. Security releases would still be provided, but not much more. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Henri Gomez wrote: Hi to all, Since many people ask for a jk2 release, 2.0.4, I'll act as release manager if nobody else want to take the job before Friday. I'd like to know what are showstoppers (blocking bugs) which should be fixed in the current release. Planning : Up to Friday 6 Feb, determine all bugs which should (could be fixed) and try to fix the blocking bugs. On Thursday 12 Feb, tag the CVS with jk2_2_0_4_rc1, make build and tests. If everything goes fine, on 13 Feb, tag the CVS with jk2_2_0_4, make tarball, and binaries (need help here for windows, netware, macosx, ...). Comments welcome I have run a watchdog tests (with Apache-2.0.47 on Linux) it returns the following (additional) errors with using mod_jk2: +++ [java] [watchdog] FAILED HttpServletResponseWrapperSetStatusMsgTest [java] [watchdog] FAILED WithLeadingSlashTest [java] [watchdog] FAILED WithoutLeadingSlashTest +++ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Henri Gomez wrote: Remy Maucherat a écrit : Bill Barker wrote: committers as binding votes). In the unlikely event that we get enough people to care about 3.3 enough to vote (seeing the trouble that Remy has getting people to vote :) You're torturing me. I thinnk you should be able to get enough +1s, though (you, Henri, JF, Larry; that's four already). And may be Costin also :) :-) I don't have a lot of time - but for a 3.3.2 I'll try to find a weekend to test it with jk2 and update the jmx interceptor if needed. so I can vote +1. Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jk2 2.0.4 release plan
Hi to all, Since many people ask for a jk2 release, 2.0.4, I'll act as release manager if nobody else want to take the job before Friday. I'd like to know what are showstoppers (blocking bugs) which should be fixed in the current release. Planning : Up to Friday 6 Feb, determine all bugs which should (could be fixed) and try to fix the blocking bugs. On Thursday 12 Feb, tag the CVS with jk2_2_0_4_rc1, make build and tests. If everything goes fine, on 13 Feb, tag the CVS with jk2_2_0_4, make tarball, and binaries (need help here for windows, netware, macosx, ...). Comments welcome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Henri Gomez wrote: Hi to all, Since many people ask for a jk2 release, 2.0.4, I'll act as release manager if nobody else want to take the job before Friday. I'd like to know what are showstoppers (blocking bugs) which should be fixed in the current release. Planning : Up to Friday 6 Feb, determine all bugs which should (could be fixed) and try to fix the blocking bugs. On Thursday 12 Feb, tag the CVS with jk2_2_0_4_rc1, make build and tests. If everything goes fine, on 13 Feb, tag the CVS with jk2_2_0_4, make tarball, and binaries (need help here for windows, netware, macosx, ...). +1, great :) As for the issues I have with mod_jk 2: - From the feedback I got from support issues, it seems LB only works with the worker MPM on Apache 2. With the default MPM (which is threaded I think), all requests go to the first node (but failover works fine, that's already something). (maybe this has been fixed already) - Failover with POST requests also seems to have issues (although it's definitely something complex, and since buffering is needed, we may not want to fix this issue). There's the exact same problem with HTTP LB, obviously. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Hi, Since many people ask for a jk2 release, 2.0.4, I'll act as release manager if nobody else want to take the job before Friday. great, thanks! Comments welcome two things I would like to discuss: 1) I would like to see all binaries packed to tar.gz or zip; this is definitely better in two ways: the original file timestamp keeps intact, and if the download is broken normally the archiver reports that. Oh, I've just checked, and this is only true for win32 and netware with mod_jk, with mod_jk2 win32 has zip... please Mike, can you put up zip files instead of renamed NLMs - also with future mod_jk releases? 2) ask for a reason why the file extension was not changed to .so on Win32 when Apache 1.3.15 moved to this...? thanks, Guenter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Günter Knauf a écrit : Hi, Since many people ask for a jk2 release, 2.0.4, I'll act as release manager if nobody else want to take the job before Friday. great, thanks! Comments welcome two things I would like to discuss: 1) I would like to see all binaries packed to tar.gz or zip; Well it could be done easily, if nobody object, I'll choose .gz for Unixes and .zip for Windows. this is definitely better in two ways: the original file timestamp keeps intact, and if the download is broken normally the archiver reports that. Oh, I've just checked, and this is only true for win32 and netware with mod_jk, with mod_jk2 win32 has zip... please Mike, can you put up zip files instead of renamed NLMs - also with future mod_jk releases? 2) ask for a reason why the file extension was not changed to .so on Win32 when Apache 1.3.15 moved to this...? Do you want it to revert to .dll ? On my Windows box the Apache 2.0.47 came with module named .so and not .dll. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
I'll be happy to deliver zips instead of NLMS. for NetWare. Henri (and others) since we are tagging and releasing jk2 can/should we do the same for jk since I know there is added functionality (Ping/Pong and timeouts) there as well? Thanks, Mike Anderson [EMAIL PROTECTED] 2/3/2004 9:27:14 AM Hi, Since many people ask for a jk2 release, 2.0.4, I'll act as release manager if nobody else want to take the job before Friday. great, thanks! Comments welcome two things I would like to discuss: 1) I would like to see all binaries packed to tar.gz or zip; this is definitely better in two ways: the original file timestamp keeps intact, and if the download is broken normally the archiver reports that. Oh, I've just checked, and this is only true for win32 and netware with mod_jk, with mod_jk2 win32 has zip... please Mike, can you put up zip files instead of renamed NLMs - also with future mod_jk releases? 2) ask for a reason why the file extension was not changed to .so on Win32 when Apache 1.3.15 moved to this...? thanks, Guenter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
I think Guenter is asking that we change mod_jk2 do be .so. Right now we build a .dll (at least if we build from the project files) but it would be easy to change this to .so and I'd be happy to do it. Mike Anderson [EMAIL PROTECTED] 2/3/2004 9:57:00 AM Günter Knauf a écrit : Hi, Since many people ask for a jk2 release, 2.0.4, I'll act as release manager if nobody else want to take the job before Friday. great, thanks! Comments welcome two things I would like to discuss: 1) I would like to see all binaries packed to tar.gz or zip; Well it could be done easily, if nobody object, I'll choose .gz for Unixes and .zip for Windows. this is definitely better in two ways: the original file timestamp keeps intact, and if the download is broken normally the archiver reports that. Oh, I've just checked, and this is only true for win32 and netware with mod_jk, with mod_jk2 win32 has zip... please Mike, can you put up zip files instead of renamed NLMs - also with future mod_jk releases? 2) ask for a reason why the file extension was not changed to .so on Win32 when Apache 1.3.15 moved to this...? Do you want it to revert to .dll ? On my Windows box the Apache 2.0.47 came with module named .so and not .dll. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Mike Anderson a écrit : I'll be happy to deliver zips instead of NLMS. for NetWare. Henri (and others) since we are tagging and releasing jk2 can/should we do the same for jk since I know there is added functionality (Ping/Pong and timeouts) there as well? Well, one release at a time, users urge us for jk2 release, jk release could wait some time (Bill ?) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Henri, What is the current state of JK2. Is it alpha, beta or GA. If this is going to be an alpha release, what is the plan for a GA release. I would like to migrate from JK when it is stable. Cheers. Dave. Henri Gomez wrote: Hi to all, Since many people ask for a jk2 release, 2.0.4, I'll act as release manager if nobody else want to take the job before Friday. I'd like to know what are showstoppers (blocking bugs) which should be fixed in the current release. Planning : Up to Friday 6 Feb, determine all bugs which should (could be fixed) and try to fix the blocking bugs. On Thursday 12 Feb, tag the CVS with jk2_2_0_4_rc1, make build and tests. If everything goes fine, on 13 Feb, tag the CVS with jk2_2_0_4, make tarball, and binaries (need help here for windows, netware, macosx, ...). Comments welcome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- * Dave Oxley * * +44 (0)7966 249 344 * * * * [EMAIL PROTECTED] * * mailto:[EMAIL PROTECTED] * * * * http://www.daveoxley.co.uk * * http://www.daveoxley.co.uk * * Linux: Because reboots are for hardware upgrades! * * * * * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jk2 2.0.4 release plan
Dave Oxley wrote: Henri, What is the current state of JK2. Is it alpha, beta or GA. If this is going to be an alpha release, what is the plan for a GA release. I would like to migrate from JK when it is stable. This is a *very* good question. Last time I dared to ask the consensus was mod_jk was a better idea for a production system -- but there was a good deal of dissent on this question... -- Jess Holle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
