+1 for the plan. Removing "src/native" from the source distribution won't be a problem. I would also be in favor of deleting the src/native/mod_jk from the CVS tree since this was moved long ago to jakarta-tomcat-connectors. If someone really wants that old version, they can grab an old source distribution or checkout the "tomcat_331_final" tag from CVS. For historical reasons, we should probably keep the src/native/jserv since it doesn't exist elsewhere.
As for the character encoding changes, it looks like the minimum that avoids regression would be to modify org.apache.tomcat.core.Request to call both setEncoding() and setQueryStringEncoding() on the Parameters object. However, this would not be supportive of the W3C standard. To support that, the new connector properties that were added to Tomcat 4 and 5 would need to be supported. I'm +0 for doing that since I think the standard is a bit flawed when applied to HTTP, thanks largely to the query string issue. I'll volunteer to include the new properties if this is desired by others. Also, I have karma for adding versions to Bugzilla, so I'll volunteer to handle that as well. Cheers, Larry > -----Original Message----- > From: Bill Barker [mailto:[EMAIL PROTECTED] > Sent: Sunday, February 08, 2004 10:12 PM > To: Tomcat Developers List > Subject: Re: [PROPOSAL] Release the HEAD of j-t as Tomcat 3.3.2 > > > Adding a couple of points I left out: > > 1) Include in the [VOTE] the provision that future TC 3.3 > releases are > governed by the TC 4/5 release-then-vote-on-status model. It > is likely that > future releases are going to be just security-related, so > streamlining is > good :). > 2) I really don't have any itches left with TC 3.3. While > I'm more than > happy to continue supporting it, should we formally announce > 3.3.2 as an EOL > release? I'm, personally -0. > > ----- Original Message ----- > From: "Bill Barker" <[EMAIL PROTECTED]> > To: "Tomcat Developers List" <[EMAIL PROTECTED]> > Sent: Sunday, February 08, 2004 6:48 PM > Subject: [PROPOSAL] Release the HEAD of j-t as Tomcat 3.3.2 > > > > It has been a long time since the 3.3.1 release, and there > are several > > important bug fixes in the CVS. Therefore, I'm proposing > cutting a 3.3.2 > > release with myself as RM (although I'll step aside if > Larry really wants > > the job :). > > > > Time Line: > > This proposal will run until Thursday, Feb 12 (I was > going to do Friday, > > until I noticed that the date was the 13th :) 6:00 PM PDT. > At that point > it > > will become a [VOTE] that will last until Thursday, Feb 19 > 6:00 PM PDT. > If > > the [VOTE] passes with 3 PMC +1s and no -1s and the > enhancements below are > > complete (with the possible exception of licensing), then we cut a > 3.3.2-RC1 > > release. I don't see that it is likely that we have any major > regressions, > > so I don't see the need for a Beta. I propose to leave RC1 > out for two > > weeks until Friday, Mar 5 (March 4th isn't good for me). > At that point we > > cut a 3.3.2 release. > > > > Packaging Changes: > > I propose that we no longer ship src/native with the src > distro (unless > it > > is too hard to modify Larry's scripts, in which case we include a > do-not-use > > in the release notes). I'd also like to include the commons-daemon > > procrun/w and jsvc (source) with the release, similar to TC > 5. Also I'd > > like to make the CoyoteConnector2 (possible renamed to > CoyoteConnector :) > > the default connector in server.xml. We can add a note to > use the old > > Connectors for people that can't use Java2. > > > > Code Changes: > > 1) I'd like to add a blocking option to o.a.t.startup.Main (e.g. > 'startb') > > so that 3.3 can be used with procrun. Also make sure that the > > init/start/stop/destroy semantics are there for jsvc. > > 2) Add fix for Bug #8643 (allow to specify alternate > module.xml files) > > 3) Port the requestURI encoding fixes for TC 4/5 > (although, I believe > that > > this is on DecodeInterceptor, instead of the Connector). > > 4) Update license to Apache-2.0 (non-negotiable, with a > March release > date > > :). > > > > Bugs: > > Several of the LATER bugs have been already fixed, so mark > them as such. > Of > > the remaining 18 open bugs, they will be marked as one of > > INVALID/FIXED/WORKSFORME/LATER. > > > > Comments/Suggestions/Flames? > > > > > > > -------------------------------------------------------------- > -------------- > ---- > > > > > > This message is intended only for the use of the person(s) > listed above as > the intended recipient(s), and may contain information that > is PRIVILEGED > and CONFIDENTIAL. If you are not an intended recipient, you > may not read, > copy, or distribute this message or any attachment. If you > received this > communication in error, please notify us immediately by > e-mail and then > delete all copies of this message and any attachments. > > > > In addition you should be aware that ordinary (unencrypted) > e-mail sent > through the Internet is not secure. Do not send confidential > or sensitive > information, such as social security numbers, account > numbers, personal > identification numbers and passwords, to us via ordinary (unencrypted) > e-mail. > > > > > > > -------------------------------------------------------------- > -------------- > ---- > > > > > --------------------------------------------------------------------- > > 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]
