TC 3.2.2 release

[GOMEZ Henri]

Hi,

Did there is a date for the 3.2.2 release ?

Just to be sure the RPM will be done ASAP


-
Henri Gomez ___[_]
EMAIL : [EMAIL PROTECTED](. .) 
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 

[RESULT] Tomcat 3.2.2 Release Plan

[Marc Saegesser]

Voting is now complete for the Tomcat 3.2.2 Release Plan.

The vote results are as follows:

   [9] +1   I am in favor of this plan and will help
   [3] +0   I am in favor of this plan, but am unable to help
   [0] -0   I am not in favor of this plan
   [0] -1   I am against this plan being executed, and my
reason is:

By this vote the release plan has been approved.

As per the release plan document, the tomcat_32 CVS branch will be frozen on
Feb 25, 2001 and the beta release follow shortly there after.


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

Re: [VOTE] Tomcat 3.2.2 Release Plan

[Mike Anderson]

Tomcat 3.2.2 Release Plan Ballot:

  [X] +1I am in favor of this plan and will help
  [ ] +0I am in favor of this plan, but am unable to help
  [ ] -0I am not in favor of this plan
  [ ] -1I am against this plan being executed, and my
reason is:

I will test on NetWare and continue to provide native connectors
for the NetWare platform.

Mike Anderson
Senior Software Engineer
Platform Services Group
[EMAIL PROTECTED]
Novell, Inc., the leading provider of Net services software
www.novell.com


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

Re: [VOTE] Tomcat 3.2.2 Release Plan

[Kief Morris]

Marc Saegesser typed the following on 09:21 AM 2/11/2001 -0600
><- Please return this portion with your vote ->
>
>Tomcat 3.2.2 Release Plan Ballot:
>
>  [X] +1   I am in favor of this plan and will help
>  [ ] +0I am in favor of this plan, but am unable to help
>  [ ] -0I am not in favor of this plan
>  [ ] -1   I am against this plan being executed, and my
>reason is:
>
>
><->


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

RE: [VOTE] Tomcat 3.2.2 Release Plan

[Larry Isaacs]

Tomcat 3.2.2 Release Plan Ballot:

  [X] +1I am in favor of this plan and will help
  [ ] +0I am in favor of this plan, but am unable to help
  [ ] -0I am not in favor of this plan
  [ ] -1I am against this plan being executed, and my
reason is:


Larry Isaacs

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

Re: [VOTE] Tomcat 3.2.2 Release Plan

[Glenn Nielsen]

Marc Saegesser wrote:
> 
> Tomcat 3.2.2 Release Plan Ballot:
> 
>   [X] +1I am in favor of this plan and will help
>   [ ] +0I am in favor of this plan, but am unable to help
>   [ ] -0I am not in favor of this plan
>   [ ] -1I am against this plan being executed, and my
> reason is:
> 

I can test on Solaris sparc/x86 JRE 1.3 and FreeBSD 3.x with jdk1.2 beta.
And test with the java security manager enabled.

Regards,

Glenn

--
Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder|
MOREnet System Programming   |  * if iz ina coment.  |
Missouri Research and Education Network  |  */   |
--

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

Re: [VOTE] Tomcat 3.2.2 Release Plan

[Dan Milstein]

Jon,

No, it's not in the release plan.  Henri had proposed it at the end of last
week (in an email, not in a plan).  We need to discuss it on the list, but,
unless someone convinces me otherwise, I don't support it -- there has been
work done on the native portions of 3.3 which is not just bug fixes, and
that shouldn't go into 3.2.2.  I'm not seeing an overriding reason for
keeping all the native code sync'd up (it's largely in sync, now, but there
are some differences).

-Dan

Jon Stevens wrote:
> 
> on 2/11/01 7:54 AM, "GOMEZ Henri" <[EMAIL PROTECTED]> wrote:
> 
> > I could help port of latest native mod_jk stuff from TC 3.3,
> > if everybody agrees. So we could have both apache 1.3 and 2.0
> > connectors, and be at the same level between TC 3.2.2/3.3
> 
> Is that in the release plan?
> 
> -jon
> 
> --
> If you come from a Perl or PHP background, JSP is a way to take
> your pain to new levels. --Anonymous
>  && 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]

-- 

Dan Milstein // [EMAIL PROTECTED]

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

Re: [VOTE] Tomcat 3.2.2 Release Plan

[Dan Milstein]

>   [X] +1I am in favor of this plan and will help
>   [ ] +0I am in favor of this plan, but am unable to help
>   [ ] -0I am not in favor of this plan
>   [ ] -1I am against this plan being executed, and my
> reason is:

-Dan
-- 

Dan Milstein // [EMAIL PROTECTED]

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

RE: [VOTE] Tomcat 3.2.2 Release Plan

[Ignacio J. Ortega]

> <- Please return this portion with your vote ->
> 
> Tomcat 3.2.2 Release Plan Ballot:
> 
>   [X] +1  I am in favor of this plan and will help
>   [ ] +0I am in favor of this plan, but am unable to help
>   [ ] -0I am not in favor of this plan
>   [ ] -1  I am against this plan being executed, and my
> reason is:
> 
> 
> <->
> 


Saludos ,
Ignacio J. Ortega


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

Re: [VOTE] Tomcat 3.2.2 Release Plan

[Hans Bergsten]

Marc Saegesser wrote:
> [...]
> Tomcat 3.2.2 Release Plan Ballot:
> 
>   [ ] +1I am in favor of this plan and will help
>   [X] +0I am in favor of this plan, but am unable to help
>   [ ] -0I am not in favor of this plan
>   [ ] -1I am against this plan being executed, and my
> reason is:

I can only help with testing.

Hans
-- 
Hans Bergsten   [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com

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

Re: [VOTE] Tomcat 3.2.2 Release Plan

[Jon Stevens]

on 2/11/01 7:21 AM, "Marc Saegesser" <[EMAIL PROTECTED]> wrote:

> [ ] +1 I am in favor of this plan and will help
> [X] +0I am in favor of this plan, but am unable to help
> [ ] -0I am not in favor of this plan
> [ ] -1 I am against this plan being executed, and my
> reason is:


-jon


-- 
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
 && 


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

Re: [VOTE] Tomcat 3.2.2 Release Plan

[Jon Stevens]

on 2/11/01 7:54 AM, "GOMEZ Henri" <[EMAIL PROTECTED]> wrote:

> I could help port of latest native mod_jk stuff from TC 3.3,
> if everybody agrees. So we could have both apache 1.3 and 2.0
> connectors, and be at the same level between TC 3.2.2/3.3

Is that in the release plan?

-jon

-- 
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
 && 


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

Re: [VOTE] Tomcat 3.2.2 Release Plan

[Remy Maucherat]

> <- Please return this portion with your vote ->
> 
> Tomcat 3.2.2 Release Plan Ballot:
> 
>   [ ] +1 I am in favor of this plan and will help
>   [X] +0I am in favor of this plan, but am unable to help
>   [ ] -0I am not in favor of this plan
>   [ ] -1 I am against this plan being executed, and my
> reason is:
> 
> 
> <->

Remy


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

Re: [VOTE] Tomcat 3.2.2 Release Plan

[cmanolache]

> Tomcat 3.2.2 Release Plan Ballot:
> 
>   [X] +1  I am in favor of this plan and will help
>   [ ] +0I am in favor of this plan, but am unable to help
>   [ ] -0I am not in favor of this plan
>   [ ] -1  I am against this plan being executed, and my
> reason is:

I'll help with the nightly builds, and I'll help review the changes 
that'll go in ( and went in ) ( we have to port some of them to 3.3 too ).
Maybe more, but 3.3 is my main priority.

Costin


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

RE: [VOTE] Tomcat 3.2.2 Release Plan

[GOMEZ Henri]

  [ ] +1I am in favor of this plan and will help
  [ ] +0I am in favor of this plan, but am unable to help
  [ ] -0I am not in favor of this plan
  [ ] -1I am against this plan being executed, and my
reason is:

+1 

I could help port of latest native mod_jk stuff from TC 3.3, 
if everybody agrees. So we could have both apache 1.3 and 2.0
connectors, and be at the same level between TC 3.2.2/3.3

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

RE: [VOTE] Tomcat 3.2.2 Release Plan

[Marc Saegesser]

> Tomcat 3.2.2 Release Plan Ballot:
> 
>   [X] +1  I am in favor of this plan and will help
>   [ ] +0I am in favor of this plan, but am unable to help
>   [ ] -0I am not in favor of this plan
>   [ ] -1  I am against this plan being executed, and my
> reason is:
> 
> 
> <->

Marc Saegesser


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

[VOTE] Tomcat 3.2.2 Release Plan

[Marc Saegesser]

This is the vote for the Tomcat 3.2.2 Release Plan.  This vote is to accept
the release plan document as it is currently written.  It is not the vote to
release Tomcat 3.2.2.

The release plan can be found at:

http://jakarta.apache.org/cvsweb/index.cgi/~checkout~/jakarta-tomcat/Attic/R
ELEASE-PLAN-3.2.2?rev=1.1.2.1

The voting period will end at midnight on Monday February 19, 2001.  I will
post the vote tally later that day.

<- Please return this portion with your vote ->

Tomcat 3.2.2 Release Plan Ballot:

  [ ] +1I am in favor of this plan and will help
  [ ] +0I am in favor of this plan, but am unable to help
  [ ] -0I am not in favor of this plan
  [ ] -1I am against this plan being executed, and my
reason is:


<->

For approval, there must be at least three +1 votes by Committers,
and more +1 votes than -1 votes.


Marc Saegesser


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

Re: [PATCH]: Bugrat report 723 ( unescaping/unencoding URLs ) was'Re: 3.2.2 Release?'

[cmanolache]

> Just checking back on the status of this patch, I received some email from
> someone who isn't actively on the list but has the same problem as
> originally reported in Bugrat report 723. Anyone have any feedback on the
> patch or the control characters in URL question I had?

I will work on it for 3.3 , there are few more encoding problems and I
need a bit of time. I don't think we can do it for M1, but it is on the
list and it has high priority.

( I don't know if they are checked into 3.2.x )

Costin
 



> 
> David Weinrich
> 
> - Original Message -
> From: "David Weinrich" <[EMAIL PROTECTED]>
> To: "Tomcat Dev List" <[EMAIL PROTECTED]>
> Sent: Friday, February 02, 2001 23:18
> Subject: [PATCH]: Bugrat report 723 ( unescaping/unencoding URLs ) was 'Re:
> 3.2.2 Release?'
> 
>   Thanks to everyone, that cleared things up quite a bit. Here is the patch
> for bugrat report 723 ( tomcat 3.2.x not unescaping escaped urls ). The
> patch is extremely short, and implemented a tiny bit different from the one
> I sent in for 3.2.x a while ago, the unencoding is done before the path is
> checked for other issues/security concerns to prevent unencoded stuff from
> causing these after the fact.
>   Note: I haven't yet mastered the art of Watchdog/internal tomcat tests so
> this will need to be tested a bit more thoroughly. So far the following urls
> work correctly:
> 
> http://localhost:8080/index%20%23%24.jsp
> http://localhost:8080/index%20%23%24.html
> 
> corresponding to the following filenames in the ROOT webapp dir:
> 
> 'index #$.jsp' and
> 'index #$.html'
> 
> If an error occurs in unencoding, null is returned which ends up sending a
> Not Found(404) message instead of a stack trace. This seemed to be the most
> sane way to handle the issue of improperly encoded urls. This is usually the
> result of having a value after a % that isn't two hex digits or having an
> unencoded % in the url like:
> 
> http://localhost:8080/index%%20%23%24.jsp or
> http://localhost:8080/index%zz%23%24.jsp
> 
> One last remaining concern I have: the current implementation of RequestUtil
> allows control characters to pass through without raising an exception, I am
> assuming this could possibly raise problems, and is fairly undesired. If I
> interpret http://www.ietf.org/rfc/rfc2396.txt correctly, control characters
> should not be included in URLs. If it is agreeable, I will make a patch to
> RequestUtil.URLDecode tomorrow to block characters in the ranges of 00-1f
> and 7f-9f to prevent this from being a potential problem. Thanks again!
> 
> 
> David
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
> 

-- 
Costin


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

Re: [PATCH]: Bugrat report 723 ( unescaping/unencoding URLs ) was 'Re: 3.2.2 Release?'

[David Weinrich]

Just checking back on the status of this patch, I received some email from
someone who isn't actively on the list but has the same problem as
originally reported in Bugrat report 723. Anyone have any feedback on the
patch or the control characters in URL question I had?

David Weinrich

- Original Message -
From: "David Weinrich" <[EMAIL PROTECTED]>
To: "Tomcat Dev List" <[EMAIL PROTECTED]>
Sent: Friday, February 02, 2001 23:18
Subject: [PATCH]: Bugrat report 723 ( unescaping/unencoding URLs ) was 'Re:
3.2.2 Release?'

  Thanks to everyone, that cleared things up quite a bit. Here is the patch
for bugrat report 723 ( tomcat 3.2.x not unescaping escaped urls ). The
patch is extremely short, and implemented a tiny bit different from the one
I sent in for 3.2.x a while ago, the unencoding is done before the path is
checked for other issues/security concerns to prevent unencoded stuff from
causing these after the fact.
  Note: I haven't yet mastered the art of Watchdog/internal tomcat tests so
this will need to be tested a bit more thoroughly. So far the following urls
work correctly:

http://localhost:8080/index%20%23%24.jsp
http://localhost:8080/index%20%23%24.html

corresponding to the following filenames in the ROOT webapp dir:

'index #$.jsp' and
'index #$.html'

If an error occurs in unencoding, null is returned which ends up sending a
Not Found(404) message instead of a stack trace. This seemed to be the most
sane way to handle the issue of improperly encoded urls. This is usually the
result of having a value after a % that isn't two hex digits or having an
unencoded % in the url like:

http://localhost:8080/index%%20%23%24.jsp or
http://localhost:8080/index%zz%23%24.jsp

One last remaining concern I have: the current implementation of RequestUtil
allows control characters to pass through without raising an exception, I am
assuming this could possibly raise problems, and is fairly undesired. If I
interpret http://www.ietf.org/rfc/rfc2396.txt correctly, control characters
should not be included in URLs. If it is agreeable, I will make a patch to
RequestUtil.URLDecode tomorrow to block characters in the ranges of 00-1f
and 7f-9f to prevent this from being a potential problem. Thanks again!


David


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

mod_jk TC 3.2.2 != TC 3.3 => was RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[GOMEZ Henri]

While looking updating TC 3.2.2 with mod_jk for Apache 2.0
I notice that mod_jk from TC 3.2.2 and 3.3 are still differents

I attached a list of diff without the version which are also
different in each files.

I propose that the whole TC 3.3 mod_jk native code (ap1.3, ap2.0
and common) are reimported in TC 3.2.2 to avoid confusion and
mistake, and let us be sure we at the same level.

What about ?
Who could do that ?


 jk-3.2-3.3.diff

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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[Marc Saegesser]

I think bugs that have been fixed in 3.3 should also get fixed on the 3.2
branch (assuming they apply, of course).

Enhancements made in 3.3 back ported to 3.2 only if the committer is willing
to test and support them in that release.

> -Original Message-
> From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 08, 2001 5:13 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [PROPOSAL] Tomcat 3.2.2 Release Plan
>
>
> >Yes, but for some reason (probably a repressed memory from
> >some former life)
> >I've always hated the phrase "no regressions".  :-)
>
> Did you want latest ajp12/ajp13 fixes from TC 3.3 to be
> included also in TC 3.2.2 ?
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[Marc Saegesser]

Craig,

The help you've offerred is greatly appreciated, and I'll take it as a +1.
I expect I'll have a few questions along the way, but the stuff you sent me
earlier about building the distrobutions was already a big help.

> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 08, 2001 2:49 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [PROPOSAL] Tomcat 3.2.2 Release Plan
>
>
> Marc Saegesser wrote:
>
> > We have collected quite a few good bug fixes on the tomcat_32
> branch since
> > the release of Tomcat 3.2.1.  I propose that we make a public
> release of the
> > tomcat_32 branch as Tomcat 3.2.2.  A proposed release plan can
> be found at
> >
> >
> http://jakarta.apache.org/cvsweb/index.cgi/~checkout~/jakarta-tomc
> at/Attic/R
> > ELEASE-PLAN-3.2.2?rev=1.1.2.1
> >
> > I am volunteering to be the release manager for Tomcat 3.2.2,
> unless someone
> > else really wants to do it.
> >
>
> +1 on the release plan as revised.
>
> I can help to the extent that I will assist Marc in the mechanics
> of release
> manager duties, and will do some evaluation testing on the
> candidate release
> code.  If that is not considered sufficient, then treat my vote
> as a +0 instead.
>
> Craig McClanahan
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[Keith Wannamaker]

Cvs head jakarta-tomcat is 3.3.  There is a branch for 3.2.

Keith

-Original Message-
From: kenneth topp [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 08, 2001 8:26 PM
To: [EMAIL PROTECTED]
Subject: RE: [PROPOSAL] Tomcat 3.2.2 Release Plan



Keith,

Is head 3.2.x or 3.3x?

Thanks,

Kenneth



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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[kenneth topp]

Keith,

Is head 3.2.x or 3.3x?

Thanks,

Kenneth

On Thu, 8 Feb 2001, Keith Wannamaker wrote:

> I regularly use ajpv13 to upload files > 2mb, using cvs head
> of jakarta-tomcat.
>
> Keith
>
> -Original Message-
> From: kenneth topp [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 08, 2001 6:43 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [PROPOSAL] Tomcat 3.2.2 Release Plan
>
>
>
> Henri,
>
> Can you add a >8k form posts to your test suite, as I've not been able to
> do that with Ajp13 with any combination of patches (up to and including
> your .RPM's).  I hope that this will work soon, as we need to go SSL soon,
> and we have several parts of the site that post more then 8k of form data
> (ie:  file uploads).
>
> I haven't tested if it's just file upload that's broken or all form upload
> (>8k with Ajp13).  I will try to come up with another test case soon.
>
> Kenneth Topp
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[Keith Wannamaker]

I regularly use ajpv13 to upload files > 2mb, using cvs head
of jakarta-tomcat.

Keith

-Original Message-
From: kenneth topp [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 08, 2001 6:43 PM
To: [EMAIL PROTECTED]
Subject: RE: [PROPOSAL] Tomcat 3.2.2 Release Plan



Henri,

Can you add a >8k form posts to your test suite, as I've not been able to
do that with Ajp13 with any combination of patches (up to and including
your .RPM's).  I hope that this will work soon, as we need to go SSL soon,
and we have several parts of the site that post more then 8k of form data
(ie:  file uploads).

I haven't tested if it's just file upload that's broken or all form upload
(>8k with Ajp13).  I will try to come up with another test case soon.

Kenneth Topp



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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[kenneth topp]

Henri,

Can you add a >8k form posts to your test suite, as I've not been able to
do that with Ajp13 with any combination of patches (up to and including
your .RPM's).  I hope that this will work soon, as we need to go SSL soon,
and we have several parts of the site that post more then 8k of form data
(ie:  file uploads).

I haven't tested if it's just file upload that's broken or all form upload
(>8k with Ajp13).  I will try to come up with another test case soon.

Kenneth Topp

On Thu, 8 Feb 2001, GOMEZ Henri wrote:

> >I will be able to build and test the native code for the ISAPI
> >redirector but I will need others to build/test the other native
> >components and supply them to me for inclusion into the release.
>
> >I will be able to test on WinNT/200 and probably Win9x platforms
> >but I would appreciate test reports from other developers about
> >the status of the other supported platforms.
>
> I'll provide RPM for Redhat Linux i386 and will test it on my dev
> servers.
>
> Regards
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>



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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[GOMEZ Henri]

>Yes, but for some reason (probably a repressed memory from 
>some former life)
>I've always hated the phrase "no regressions".  :-)

Did you want latest ajp12/ajp13 fixes from TC 3.3 to be
included also in TC 3.2.2 ?


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

Re: [PROPOSAL] Tomcat 3.2.2 Release Plan

[Craig R. McClanahan]

Marc Saegesser wrote:

> We have collected quite a few good bug fixes on the tomcat_32 branch since
> the release of Tomcat 3.2.1.  I propose that we make a public release of the
> tomcat_32 branch as Tomcat 3.2.2.  A proposed release plan can be found at
>
> http://jakarta.apache.org/cvsweb/index.cgi/~checkout~/jakarta-tomcat/Attic/R
> ELEASE-PLAN-3.2.2?rev=1.1.2.1
>
> I am volunteering to be the release manager for Tomcat 3.2.2, unless someone
> else really wants to do it.
>

+1 on the release plan as revised.

I can help to the extent that I will assist Marc in the mechanics of release
manager duties, and will do some evaluation testing on the candidate release
code.  If that is not considered sufficient, then treat my vote as a +0 instead.

Craig McClanahan



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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[Marc Saegesser]

Yes, but for some reason (probably a repressed memory from some former life)
I've always hated the phrase "no regressions".  :-)

> -Original Message-
> From: James Duncan Davidson [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 07, 2001 9:41 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [PROPOSAL] Tomcat 3.2.2 Release Plan
>
>
> on 2/7/01 5:12 PM, Marc Saegesser at [EMAIL PROTECTED] wrote:
>
> > Any bug introduced by a code change since Tomcat 3.2.1 was released MUST
> > be fixed.  If it worked in 3.2.1 it will work in 3.2.2.
>
> "no regressions" I think is the term that you are looking for.
>
> --
> James Duncan Davidson
> http://x180.net/ !try; do();
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[Ignacio J. Ortega]

+1 

Saludos ,
Ignacio J. Ortega


> -Mensaje original-
> De: Marc Saegesser [mailto:[EMAIL PROTECTED]]
> Enviado el: jueves 8 de febrero de 2001 0:35
> Para: [EMAIL PROTECTED]
> Asunto: [PROPOSAL] Tomcat 3.2.2 Release Plan
> 
> 
> We have collected quite a few good bug fixes on the tomcat_32 
> branch since
> the release of Tomcat 3.2.1.  I propose that we make a public 
> release of the
> tomcat_32 branch as Tomcat 3.2.2.  A proposed release plan 
> can be found at
> 
> http://jakarta.apache.org/cvsweb/index.cgi/~checkout~/jakarta-
> tomcat/Attic/R
> ELEASE-PLAN-3.2.2?rev=1.1.2.1
> 
> I am volunteering to be the release manager for Tomcat 3.2.2, 
> unless someone
> else really wants to do it.
> 
> The goal for this release is not to fix every known problem 
> in Tomcat 3.2.1
> but to make the current set of fixes publicly available.  It 
> would be great
> if everything could get fixed but in the interest of timely 
> bug fixes for
> users with production systems I think we need to get what we 
> have out there.
> Once 3.2.2 is finalized, development can continue to fix 
> additional bugs and
> subsequent 3.2.x release can be made as needed.
> 
> Please review and comment on the proposed release plan.  I 
> will call release
> plan vote in the near future.
> 
> I will be able to build and test the native code for the 
> ISAPI redirector
> but I will need others to build/test the other native 
> components and supply
> them to me for inclusion into the release.  I will be able to test on
> WinNT/200 and probably Win9x platforms but I would appreciate 
> test reports
> from other developers about the status of the other supported 
> platforms.
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
> 
> 

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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[GOMEZ Henri]

>I will be able to build and test the native code for the ISAPI
>redirector but I will need others to build/test the other native
>components and supply them to me for inclusion into the release. 

>I will be able to test on WinNT/200 and probably Win9x platforms
>but I would appreciate test reports from other developers about
>the status of the other supported platforms.

I'll provide RPM for Redhat Linux i386 and will test it on my dev
servers.

Regards 

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

Re: [PROPOSAL] Tomcat 3.2.2 Release Plan

[James Duncan Davidson]

on 2/7/01 5:12 PM, Marc Saegesser at [EMAIL PROTECTED] wrote:

> Any bug introduced by a code change since Tomcat 3.2.1 was released MUST
> be fixed.  If it worked in 3.2.1 it will work in 3.2.2.

"no regressions" I think is the term that you are looking for.

-- 
James Duncan Davidson
http://x180.net/ !try; do();


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

RE: [PROPOSAL] Tomcat 3.2.2 Release Plan

[Marc Saegesser]

How about the following:

Any bug introduced by a code change since Tomcat 3.2.1 was released MUST
be fixed.  If it worked in 3.2.1 it will work in 3.2.2.

All Bugzilla items opened against "Tocmat 3" must be marked as RESOLVED.
Those items that are not going to be fixed in Tomcat 3.2.2 will be given
a resolution of LATER.  After Tomcat 3.2.2 is released items marked LATER
will be re-opened and may then be addressed in a future release.

I am currently reviewing all open Bugzilla items and I've found several
things have have been fixed but the BugRat/Bugzilla report has not been
updated.  I would greatly appreciate it if any committer who has made
changes to the tomcat_32 branch in the last several months would make sure
that the bugs they have fixed are marked appropriately.

> -Original Message-
> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 07, 2001 6:20 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [PROPOSAL] Tomcat 3.2.2 Release Plan
>
>
> on 2/7/01 3:34 PM, "Marc Saegesser" <[EMAIL PROTECTED]> wrote:
>
> > Please review and comment on the proposed release plan.  I will
> call release
> > plan vote in the near future.
>
> +0 if and only if (ie: not -1) the following is modified to state:
>
> "Any bug introduced after Tomcat 3.2.1 MUST be fixed."
>
> changed to:
>
> Any bug introduced after Tomcat 3.2.1 MUST be marked with a
> status of CLOSED
> and a resolution of FIXED or LATER. After the release of Tomcat 3.2.2, all
> bugs marked LATER will be marked as OPEN again so that they can
> be fixed in
> future versions.
>
> thanks,
>
> -jon
>
> --
> If you come from a Perl or PHP background, JSP is a way to take
> your pain to new levels. --Anonymous
> <http://jakarta.apache.org/velocity/> && <http://java.apache.org/turbine/>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


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

Re: [PROPOSAL] Tomcat 3.2.2 Release Plan

[Jon Stevens]

on 2/7/01 3:34 PM, "Marc Saegesser" <[EMAIL PROTECTED]> wrote:

> Please review and comment on the proposed release plan.  I will call release
> plan vote in the near future.

+0 if and only if (ie: not -1) the following is modified to state:

"Any bug introduced after Tomcat 3.2.1 MUST be fixed."

changed to:

Any bug introduced after Tomcat 3.2.1 MUST be marked with a status of CLOSED
and a resolution of FIXED or LATER. After the release of Tomcat 3.2.2, all
bugs marked LATER will be marked as OPEN again so that they can be fixed in
future versions.

thanks,

-jon

-- 
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
 && 


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

[PROPOSAL] Tomcat 3.2.2 Release Plan

[Marc Saegesser]

We have collected quite a few good bug fixes on the tomcat_32 branch since
the release of Tomcat 3.2.1.  I propose that we make a public release of the
tomcat_32 branch as Tomcat 3.2.2.  A proposed release plan can be found at

http://jakarta.apache.org/cvsweb/index.cgi/~checkout~/jakarta-tomcat/Attic/R
ELEASE-PLAN-3.2.2?rev=1.1.2.1

I am volunteering to be the release manager for Tomcat 3.2.2, unless someone
else really wants to do it.

The goal for this release is not to fix every known problem in Tomcat 3.2.1
but to make the current set of fixes publicly available.  It would be great
if everything could get fixed but in the interest of timely bug fixes for
users with production systems I think we need to get what we have out there.
Once 3.2.2 is finalized, development can continue to fix additional bugs and
subsequent 3.2.x release can be made as needed.

Please review and comment on the proposed release plan.  I will call release
plan vote in the near future.

I will be able to build and test the native code for the ISAPI redirector
but I will need others to build/test the other native components and supply
them to me for inclusion into the release.  I will be able to test on
WinNT/200 and probably Win9x platforms but I would appreciate test reports
from other developers about the status of the other supported platforms.


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

[PATCH]: Bugrat report 723 ( unescaping/unencoding URLs ) was 'Re: 3.2.2 Release?'

[David Weinrich]

  Thanks to everyone, that cleared things up quite a bit. Here is the patch
for bugrat report 723 ( tomcat 3.2.x not unescaping escaped urls ). The
patch is extremely short, and implemented a tiny bit different from the one
I sent in for 3.2.x a while ago, the unencoding is done before the path is
checked for other issues/security concerns to prevent unencoded stuff from
causing these after the fact.
  Note: I haven't yet mastered the art of Watchdog/internal tomcat tests so
this will need to be tested a bit more thoroughly. So far the following urls
work correctly:

http://localhost:8080/index%20%23%24.jsp
http://localhost:8080/index%20%23%24.html

corresponding to the following filenames in the ROOT webapp dir:

'index #$.jsp' and
'index #$.html'

If an error occurs in unencoding, null is returned which ends up sending a
Not Found(404) message instead of a stack trace. This seemed to be the most
sane way to handle the issue of improperly encoded urls. This is usually the
result of having a value after a % that isn't two hex digits or having an
unencoded % in the url like:

http://localhost:8080/index%%20%23%24.jsp or
http://localhost:8080/index%zz%23%24.jsp

One last remaining concern I have: the current implementation of RequestUtil
allows control characters to pass through without raising an exception, I am
assuming this could possibly raise problems, and is fairly undesired. If I
interpret http://www.ietf.org/rfc/rfc2396.txt correctly, control characters
should not be included in URLs. If it is agreeable, I will make a patch to
RequestUtil.URLDecode tomorrow to block characters in the ranges of 00-1f
and 7f-9f to prevent this from being a potential problem. Thanks again!


David

- Original Message -
From: "Marc Saegesser" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 02, 2001 12:44
Subject: RE: 3.2.2 Release?


> You are correct, tomcat_32 is the appropriate tag.  tomcat_32 is a branch
> tag so if you use cvs to check out jakarta-tomcat like
>
> cvs co -r tomcat_32 jakarta-tomcat
>
> then you'll get the latest version of all files on this branch.  This is
> referred to as the "tip" of the branch.
>
> The labels like tomcat_32_final and tomcat_321_final label a particular
> version of a file so the command
>
> cvs co -r tomcat_321_final jakarta-tomcat
>
> will retrieve the versions of all the files that make up the Tomcat 3.2.1
> release.
>
> The code that is (most likely) destined to become Tomcat 3.3 is the main
> branch of the repository, often referred to as the "HEAD".  To get this
code
> from cvs use a command like
>
> cvs co jakarta-tomcat
>
> When Tomcat 3.3 is released a new branch will be created called tomcat_33
> and this will form the basis for all bug fixes and patches for the 3.3
> release.  The HEAD will then become the code base for any new feature
> development of the 3.x repository.
>
> > -Original Message-
> > From: David Weinrich [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, February 02, 2001 2:31 PM
> > To: Tomcat Dev List
> > Subject: Re: 3.2.2 Release?
> >
> >
> > On a somewhat unrelated note...
> >   I noticed a bugrat report this morning on an urlencoding that I had
> > submitted a patch for a little while back ( which was
flawed/incomplete ).
> > In the process of redoing the patch and grabbing the source from
> > cvs I came
> > up against this issue: what the heck tag is appropriate to use to submit
> > bugfixes against for the 3.2.x version of Tomcat? I am assuming that
> > tomcat_32 is the appropriate place but...
> >
> >
> >
> > - Original Message -
> > From: "Marc Saegesser" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Friday, February 02, 2001 11:04
> > Subject: RE: 3.2.2 Release?
> >
> >
> > > One thing I don't see listed here, and is the biggest reason I
> > don't think
> > I
> > > have the time to manage the release, is determining what bugs
> > still exist
> > in
> > > the tomcat_32 branch and which of those, if any, should be fixed
before
> > > releasing 3.2.2.  This was an issue that Jon raised regarding the 3.3
> > > release plan.  What is the feeling of the Tomcat development
community?
> > Can
> > > we get away with just releasing the tip of tomcat_32 as-is or
> > would such a
> > > release *require* a complete review of open bugs and should the
> > release be
> > > held until these bugs are all addressed.
> > >
> > > I've been trying to make just such a review but it has been very time
> > > consuming.  Maybe, since t

RE: 3.2.2 Release?

[Marc Saegesser]

You are correct, tomcat_32 is the appropriate tag.  tomcat_32 is a branch
tag so if you use cvs to check out jakarta-tomcat like

cvs co -r tomcat_32 jakarta-tomcat

then you'll get the latest version of all files on this branch.  This is
referred to as the "tip" of the branch.

The labels like tomcat_32_final and tomcat_321_final label a particular
version of a file so the command

cvs co -r tomcat_321_final jakarta-tomcat

will retrieve the versions of all the files that make up the Tomcat 3.2.1
release.

The code that is (most likely) destined to become Tomcat 3.3 is the main
branch of the repository, often referred to as the "HEAD".  To get this code
from cvs use a command like

cvs co jakarta-tomcat

When Tomcat 3.3 is released a new branch will be created called tomcat_33
and this will form the basis for all bug fixes and patches for the 3.3
release.  The HEAD will then become the code base for any new feature
development of the 3.x repository.

> -Original Message-
> From: David Weinrich [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 02, 2001 2:31 PM
> To: Tomcat Dev List
> Subject: Re: 3.2.2 Release?
>
>
> On a somewhat unrelated note...
>   I noticed a bugrat report this morning on an urlencoding that I had
> submitted a patch for a little while back ( which was flawed/incomplete ).
> In the process of redoing the patch and grabbing the source from
> cvs I came
> up against this issue: what the heck tag is appropriate to use to submit
> bugfixes against for the 3.2.x version of Tomcat? I am assuming that
> tomcat_32 is the appropriate place but...
>
>
>
> - Original Message -
> From: "Marc Saegesser" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, February 02, 2001 11:04
> Subject: RE: 3.2.2 Release?
>
>
> > One thing I don't see listed here, and is the biggest reason I
> don't think
> I
> > have the time to manage the release, is determining what bugs
> still exist
> in
> > the tomcat_32 branch and which of those, if any, should be fixed before
> > releasing 3.2.2.  This was an issue that Jon raised regarding the 3.3
> > release plan.  What is the feeling of the Tomcat development community?
> Can
> > we get away with just releasing the tip of tomcat_32 as-is or
> would such a
> > release *require* a complete review of open bugs and should the
> release be
> > held until these bugs are all addressed.
> >
> > I've been trying to make just such a review but it has been very time
> > consuming.  Maybe, since this is just a minor point release to
> an existing
> > product, we can go with what we have.
> >
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


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

Re: 3.2.2 Release?

[Dan Milstein]

tomcat_32 is the right place -- it is a branch which is up to date for all
fixes which have been made against 3.2 (including 3.2.1).  The other various
3.2 looking things in cvs (e.g. 321_final) are tags but not branches.

I'm working on urlencoding stuff right now, so I await your patch with bated
breath ;-).

-Dan

David Weinrich wrote:
> 
> On a somewhat unrelated note...
>   I noticed a bugrat report this morning on an urlencoding that I had
> submitted a patch for a little while back ( which was flawed/incomplete ).
> In the process of redoing the patch and grabbing the source from cvs I came
> up against this issue: what the heck tag is appropriate to use to submit
> bugfixes against for the 3.2.x version of Tomcat? I am assuming that
> tomcat_32 is the appropriate place but...

-- 

Dan Milstein // [EMAIL PROTECTED]

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

Re: 3.2.2 Release?

[Craig R. McClanahan]

David Weinrich wrote:

> On a somewhat unrelated note...
>   I noticed a bugrat report this morning on an urlencoding that I had
> submitted a patch for a little while back ( which was flawed/incomplete ).
> In the process of redoing the patch and grabbing the source from cvs I came
> up against this issue: what the heck tag is appropriate to use to submit
> bugfixes against for the 3.2.x version of Tomcat? I am assuming that
> tomcat_32 is the appropriate place but...
>

Yes, that is the correct place -- "tomcat_32" is a branch that contains the
current state of the 3.2 codebase (i.e. all the patches for 3.2.1, plus patches
that have been committed since then).

Craig



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

Re: 3.2.2 Release?

[David Weinrich]

On a somewhat unrelated note...
  I noticed a bugrat report this morning on an urlencoding that I had
submitted a patch for a little while back ( which was flawed/incomplete ).
In the process of redoing the patch and grabbing the source from cvs I came
up against this issue: what the heck tag is appropriate to use to submit
bugfixes against for the 3.2.x version of Tomcat? I am assuming that
tomcat_32 is the appropriate place but...



- Original Message -
From: "Marc Saegesser" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 02, 2001 11:04
Subject: RE: 3.2.2 Release?


> One thing I don't see listed here, and is the biggest reason I don't think
I
> have the time to manage the release, is determining what bugs still exist
in
> the tomcat_32 branch and which of those, if any, should be fixed before
> releasing 3.2.2.  This was an issue that Jon raised regarding the 3.3
> release plan.  What is the feeling of the Tomcat development community?
Can
> we get away with just releasing the tip of tomcat_32 as-is or would such a
> release *require* a complete review of open bugs and should the release be
> held until these bugs are all addressed.
>
> I've been trying to make just such a review but it has been very time
> consuming.  Maybe, since this is just a minor point release to an existing
> product, we can go with what we have.
>




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

Re: 3.2.2 Release?

[Mike Anderson]

I don't have commit access so can't help there, but I would like to get the
3.2 versions of the NetWare binaries updated in the builds area
(builds/jakarta-tomcat/release/)

If we do get nightly builds or do a milestone, or whatever, who should the
lucky :-) recipient be?

Mike Anderson
Senior Software Engineer
Platform Services Group
[EMAIL PROTECTED]
Novell, Inc., the leading provider of Net services software
www.novell.com

>>> [EMAIL PROTECTED] 02/02/01 11:24AM >>>
Can someone who has functioned as a release manager for a dot release give
me a quick overview of what's involved?  I may be able to find the time, but
I'm not totally clear on the scope of what needs to happen.

I don't think Milestone releases would make sense -- from what it says on
http://jakarta.apache.org/site/binindex.html, those sound like they should
really be steps towards a major release of new functionality, not snapshots
of bug fixes in a released product.   Nightly builds I would be fine with,
however.

-Dan

[EMAIL PROTECTED] wrote:
> 
> > I'm in the same boat right now.  I'd love to a 3.2.2 released but I'm way
> > too busy right now to manage a release.
> 
> What about a "milestone" ? It doesn't have all the requirements of a
> release. I can add a nightly build of 3.2.x to my scripts too ? ( it'll
> not be a "blessed" release, but people who need the patches can use it ).
> 
> Costin
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED] 
> For additional commands, email: [EMAIL PROTECTED] 

-- 

Dan Milstein // [EMAIL PROTECTED] 

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



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

RE: 3.2.2 Release?

[Marc Saegesser]

One thing I don't see listed here, and is the biggest reason I don't think I
have the time to manage the release, is determining what bugs still exist in
the tomcat_32 branch and which of those, if any, should be fixed before
releasing 3.2.2.  This was an issue that Jon raised regarding the 3.3
release plan.  What is the feeling of the Tomcat development community?  Can
we get away with just releasing the tip of tomcat_32 as-is or would such a
release *require* a complete review of open bugs and should the release be
held until these bugs are all addressed.

I've been trying to make just such a review but it has been very time
consuming.  Maybe, since this is just a minor point release to an existing
product, we can go with what we have.

> -Original Message-
> From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 02, 2001 12:44 PM
> To: [EMAIL PROTECTED]
> Subject: Re: 3.2.2 Release?
>
>
> Dan Milstein wrote:
>
> > Can someone who has functioned as a release manager for a dot
> release give
> > me a quick overview of what's involved?  I may be able to find
> the time, but
> > I'm not totally clear on the scope of what needs to happen.
> >
>
> What's involved is essentially:
> * Propose the release plan ("I propose to mark the 'tomcat_32"
>   branch on date x/y/ and release it as version 3.2.2")
>   for a vote on TOMCAT-DEV.
> * Normally, such a plan also includes a temporary freeze on
>   commits to that branch, unless you do them (to pick up last
>   minute patches) or delegate the commits for those issues.
> * If the number of changes is large enough, you might want
>   to do a "release candidate" ahead of the actual release for
>   people to bang against.  3.2.2 has had enough patches that
>   this might be a good idea.  (Nightly builds would also serve
>   this role -- it would be *great* if Costin had time to set this
>   up as part of his nightly run).
> * On the day of reckoning, do a CVS tag of the correct
>   code (probably with a tag like "tomcat_322_final").
> * Build binary and source distributions in all the usual formats,
>   and publish them to the Jakarta web site.
> * Build native code binaries for as many platforms as you can
>   gather, and publish them too.
> * Announce the release on the Jakarta web site, plus to the
>   following Jakarta mailing lists:  ANNOUNCEMENTS, GENERAL,
>   TOMCAT-DEV, and TOMCAT-USER.
>
> I can assist with questions on the mechanics, but don't have time
> to do the
> entire job.
>
>
> >
> > I don't think Milestone releases would make sense -- from what
> it says on
> > http://jakarta.apache.org/site/binindex.html, those sound like
> they should
> > really be steps towards a major release of new functionality,
> not snapshots
> > of bug fixes in a released product.   Nightly builds I would be
> fine with,
> > however.
> >
> > -Dan
> >
>
> Craig
>
>
> >
> > [EMAIL PROTECTED] wrote:
> > >
> > > > I'm in the same boat right now.  I'd love to a 3.2.2
> released but I'm way
> > > > too busy right now to manage a release.
> > >
> > > What about a "milestone" ? It doesn't have all the requirements of a
> > > release. I can add a nightly build of 3.2.x to my scripts too
> ? ( it'll
> > > not be a "blessed" release, but people who need the patches
> can use it ).
> > >
> > > Costin
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, email: [EMAIL PROTECTED]
> >
> > --
> >
> > Dan Milstein // [EMAIL PROTECTED]
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


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

Re: 3.2.2 Release?

[Craig R. McClanahan]

[EMAIL PROTECTED] wrote:

> > I'm in the same boat right now.  I'd love to a 3.2.2 released but I'm way
> > too busy right now to manage a release.
>
> What about a "milestone" ? It doesn't have all the requirements of a
> release. I can add a nightly build of 3.2.x to my scripts too ? ( it'll
> not be a "blessed" release, but people who need the patches can use it ).
>

It would be great if you had time to add a nightly build of the "tomcat_32"
branch as well.

> Costin
>

Craig



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

Re: 3.2.2 Release?

[Craig R. McClanahan]

Dan Milstein wrote:

> Can someone who has functioned as a release manager for a dot release give
> me a quick overview of what's involved?  I may be able to find the time, but
> I'm not totally clear on the scope of what needs to happen.
>

What's involved is essentially:
* Propose the release plan ("I propose to mark the 'tomcat_32"
  branch on date x/y/ and release it as version 3.2.2")
  for a vote on TOMCAT-DEV.
* Normally, such a plan also includes a temporary freeze on
  commits to that branch, unless you do them (to pick up last
  minute patches) or delegate the commits for those issues.
* If the number of changes is large enough, you might want
  to do a "release candidate" ahead of the actual release for
  people to bang against.  3.2.2 has had enough patches that
  this might be a good idea.  (Nightly builds would also serve
  this role -- it would be *great* if Costin had time to set this
  up as part of his nightly run).
* On the day of reckoning, do a CVS tag of the correct
  code (probably with a tag like "tomcat_322_final").
* Build binary and source distributions in all the usual formats,
  and publish them to the Jakarta web site.
* Build native code binaries for as many platforms as you can
  gather, and publish them too.
* Announce the release on the Jakarta web site, plus to the
  following Jakarta mailing lists:  ANNOUNCEMENTS, GENERAL,
  TOMCAT-DEV, and TOMCAT-USER.

I can assist with questions on the mechanics, but don't have time to do the
entire job.


>
> I don't think Milestone releases would make sense -- from what it says on
> http://jakarta.apache.org/site/binindex.html, those sound like they should
> really be steps towards a major release of new functionality, not snapshots
> of bug fixes in a released product.   Nightly builds I would be fine with,
> however.
>
> -Dan
>

Craig


>
> [EMAIL PROTECTED] wrote:
> >
> > > I'm in the same boat right now.  I'd love to a 3.2.2 released but I'm way
> > > too busy right now to manage a release.
> >
> > What about a "milestone" ? It doesn't have all the requirements of a
> > release. I can add a nightly build of 3.2.x to my scripts too ? ( it'll
> > not be a "blessed" release, but people who need the patches can use it ).
> >
> > Costin
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
>
> --
>
> Dan Milstein // [EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


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

Re: 3.2.2 Release?

[Dan Milstein]

Can someone who has functioned as a release manager for a dot release give
me a quick overview of what's involved?  I may be able to find the time, but
I'm not totally clear on the scope of what needs to happen.

I don't think Milestone releases would make sense -- from what it says on
http://jakarta.apache.org/site/binindex.html, those sound like they should
really be steps towards a major release of new functionality, not snapshots
of bug fixes in a released product.   Nightly builds I would be fine with,
however.

-Dan

[EMAIL PROTECTED] wrote:
> 
> > I'm in the same boat right now.  I'd love to a 3.2.2 released but I'm way
> > too busy right now to manage a release.
> 
> What about a "milestone" ? It doesn't have all the requirements of a
> release. I can add a nightly build of 3.2.x to my scripts too ? ( it'll
> not be a "blessed" release, but people who need the patches can use it ).
> 
> Costin
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]

-- 

Dan Milstein // [EMAIL PROTECTED]

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

RE: 3.2.2 Release?

[cmanolache]

> I'm in the same boat right now.  I'd love to a 3.2.2 released but I'm way
> too busy right now to manage a release.

What about a "milestone" ? It doesn't have all the requirements of a
release. I can add a nightly build of 3.2.x to my scripts too ? ( it'll
not be a "blessed" release, but people who need the patches can use it ).

Costin


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

RE: 3.2.2 Release?

[Marc Saegesser]

I'm in the same boat right now.  I'd love to a 3.2.2 released but I'm way
too busy right now to manage a release.

> -Original Message-
> From: danmil [mailto:danmil]On Behalf Of Dan Milstein
> Sent: Friday, February 02, 2001 11:24 AM
> To: [EMAIL PROTECTED]
> Subject: 3.2.2 Release?
>
>
> There was some discussion about producing a 3.2.2 release at some point
> soonish.  Where is that now?  People have contributed some excellent fixes
> in the connector area, and I would love to see those available to the
> general public.
>
> I'm not in a position to function as the Release Manager, but I can help
> collect info about what fixes have been made in the mod_jk/connector area.
>
> -Dan
> --
>
> Dan Milstein // [EMAIL PROTECTED]
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]


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

3.2.2 Release?

[Dan Milstein]

There was some discussion about producing a 3.2.2 release at some point
soonish.  Where is that now?  People have contributed some excellent fixes
in the connector area, and I would love to see those available to the
general public.

I'm not in a position to function as the Release Manager, but I can help
collect info about what fixes have been made in the mod_jk/connector area.

-Dan
-- 

Dan Milstein // [EMAIL PROTECTED]

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