Re: mod_jk 1.2.32 [was: Re: svn commit: r1127315 - /tomcat/jk/trunk/xdocs/reference/apache.xml]

2011-05-28 Thread Tim Whittington
There are enough changes for a 1.2.32 anyhows, so I would propose we start a new release cycle in about 2 weeks. OK? +1 I could give RM a go if that works for ya'll - I've done a dry run already to find where everything goes. cheers tim

mod_jk 1.2.32 [was: Re: svn commit: r1127315 - /tomcat/jk/trunk/xdocs/reference/apache.xml]

2011-05-26 Thread Rainer Jung
On 25.05.2011 00:15, Christopher Schultz wrote: All, I'm not sure what the policy is on documentation changes and back-porting to already-released versions of mod_jk, but this clarifies how mod_jk works and would be beneficial to have on the web site without having to wait for a new release

Re: mod_jk 1.2.32 [was: Re: svn commit: r1127315 - /tomcat/jk/trunk/xdocs/reference/apache.xml]

2011-05-26 Thread Christopher Schultz
Rainer, On 5/26/2011 5:06 AM, Rainer Jung wrote: There are enough changes for a 1.2.32 anyhow, so I would propose we start a new release cycle in about 2 weeks. Sounds great. -chris signature.asc Description: OpenPGP digital signature

Re: mod_jk 1.2.32 [was: Re: svn commit: r1127315 - /tomcat/jk/trunk/xdocs/reference/apache.xml]

2011-05-26 Thread Rainer Jung
On 26.05.2011 15:36, Christopher Schultz wrote: Rainer, On 5/26/2011 5:06 AM, Rainer Jung wrote: There are enough changes for a 1.2.32 anyhow, so I would propose we start a new release cycle in about 2 weeks. Sounds great. Someone looking at the IPV6 patch (BZ 43968)? Rainer

Re: mod_jk 1.2.32 [was: Re: svn commit: r1127315 - /tomcat/jk/trunk/xdocs/reference/apache.xml]

2011-05-26 Thread Mladen Turk
On 05/26/2011 04:22 PM, Rainer Jung wrote: On 26.05.2011 15:36, Christopher Schultz wrote: Rainer, On 5/26/2011 5:06 AM, Rainer Jung wrote: There are enough changes for a 1.2.32 anyhow, so I would propose we start a new release cycle in about 2 weeks. Sounds great. Someone looking at the