Re: [VOTE] 4.1.31 maintenance release

2004-08-24 Thread Rainer Jung
I think there is no clear explanation of the TC4 support situation on the tomcat web site. Maybe to be fair to users you should start by adding statements, that TC 5 is the preferred version and TC 4 is soon to be supported only for major bugs and security patches. Furthermore you could

RE: [VOTE] 4.1.31 maintenance release

2004-08-24 Thread Shapira, Yoav
: Tuesday, August 24, 2004 2:24 AM To: Tomcat Developers List Subject: Re: [VOTE] 4.1.31 maintenance release I think there is no clear explanation of the TC4 support situation on the tomcat web site. Maybe to be fair to users you should start by adding statements, that TC 5 is the preferred version

Re: [VOTE] 4.1.31 maintenance release

2004-08-23 Thread Remy Maucherat
Keith Wannamaker wrote: ballot The 4.1.31 maintenance release should happen: [X] Yes [ ] No /ballot Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] 4.1.31 maintenance release

2004-08-23 Thread Shapira, Yoav
Hola, I think we long ago agreed not to vote -1 just because you want somebody to work on a different codebase :-) It must have been long enough ago that I wasn't here ;) I don't remember it. Anyways, since is a (non-lazy) majority vote so my -1 is not a veto, just an opinion. We already had

Re: [VOTE] 4.1.31 maintenance release

2004-08-21 Thread Kurt Miller
ballot The 4.1.31 maintenance release should happen: [X ] Yes [ ] No /ballot I'd like to see the fix for bug 20148 get released on the 4.x branch. -Kurt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,

[VOTE] 4.1.31 maintenance release

2004-08-20 Thread Keith Wannamaker
Hi, I propose to apply pending bugzilla 4.1 patches and issue a 4.1.31 release. The existance of unreleased committed fixes, unapplied patches, and multiple requests for 4.1.31 on tomcat-dev clearly represent an interest in a maintenance relase of 4.1.31. I volunteer to be the RM for this

RE: [VOTE] 4.1.31 maintenance release

2004-08-20 Thread Shapira, Yoav
Hi, ballot The 4.1.31 maintenance release should happen: [ ] Yes [ X ] No /ballot -1 on this release. Reasons have been stated in detail in the other thread, but to summarize this branch is no longer maintained and users should upgrade to 5.x or custom-patch if they have an emergency. Yoav

RE: [VOTE] 4.1.31 maintenance release

2004-08-20 Thread Mark Thomas
ballot The 4.1.31 maintenance release should happen: [X] Yes [ ] No /ballot Just such a thing has been on my mind for a while. Whilst in an ideal world everyone would migrate to 5.x, I have seen many organisations prefer to stay on earlier versions of software for a variety of reasons. I

Re: [VOTE] 4.1.31 maintenance release

2004-08-20 Thread Bill Barker
ballot The 4.1.31 maintenance release should happen: [X] Yes [ ] No /ballot - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message is intended only for the

Re: [VOTE] 4.1.31 maintenance release

2004-08-20 Thread Tom Anderson
ballot The 4.1.31 maintenance release should happen: [ X ] Yes [ ] No /ballot I would benefit directly from many of the fixes. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] 4.1.31 maintenance release

2004-08-20 Thread Tim Funk
Its maintained if there is a committer who will apply the patches. Mark has been very good at doing this. For large companies - it takes (a lot) time to upgrade versions. I'm still stuck on 4.0.4 for all of my servers. (Soon to be 5 if all goes well) Stability is more important than speed and

Re: [VOTE] 4.1.31 maintenance release

2004-08-20 Thread Costin Manolache
I think we long ago agreed not to vote -1 just because you want somebody to work on a different codebase :-) If Keith has an itch in 4.1 branch - and if he can find 2 more +1 votes, than it's his right to have a release, and the 4.1 branch will become maintained. A branch is maintained if