You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mladen Turk <mt...@apache.org> on 2012/03/19 15:48:23 UTC
Release JK 1.2.34
Hi,
I plan to tag 1.2.34 tomorrow cause we have one regression
and few long lasting bugs fixed.
I'd appreciate if you can check the httpd builds from trunk
since I concentrated mainly on IIS.
BTW, should we remove/revoke 1.2.33 or just go with 1.2.34?
IMHO 1.2.33 is unusable, so that's a valid reason.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Release JK 1.2.34
Posted by Mladen Turk <mt...@apache.org>.
On 03/19/2012 04:18 PM, Mark Thomas wrote:
>>
>> Do you have any template for that?
>
> Sorry no. Maybe something like:
>
Send...
Thanks
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Release JK 1.2.34
Posted by Mark Thomas <ma...@apache.org>.
On 19/03/2012 15:07, Mladen Turk wrote:
> On 03/19/2012 03:57 PM, Mark Thomas wrote:
>> On 19/03/2012 14:55, Mark Thomas wrote:
>>> On 19/03/2012 14:48, Mladen Turk wrote:
>>>> Hi,
>>>>
>>>> I plan to tag 1.2.34 tomorrow cause we have one regression
>>>> and few long lasting bugs fixed.
>>>>
>>>> I'd appreciate if you can check the httpd builds from trunk
>>>> since I concentrated mainly on IIS.
>>>>
>>>> BTW, should we remove/revoke 1.2.33 or just go with 1.2.34?
>>>> IMHO 1.2.33 is unusable, so that's a valid reason.
>>>
>>> 1.2.33 has been released so go with 1.2.34
>>
>> Misunderstood the question. Lets just get 1.2.34 out there.
>>
>
> OK.
>
>> Might be worth an email to announce@ now for the folks not following the
>> users list.
>>
>
> Do you have any template for that?
Sorry no. Maybe something like:
The Apache Tomcat team wishes to draw your attention to stability issues
that have been identified with the recent mod_jk 1.2.33 release. If you
have not yet upgraded to mod_jk 1.2.33 we recommend that you wait for
the mod_jk 1.2.34 release which is currently in progress. If you have
upgraded and are experienced issues we recommend that you downgrade to
mod_jk 1.2.32 until mod_jk 1.2.34 is available.
We apologise for any inconvenience.
The Apache Tomcat Team
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Release JK 1.2.34
Posted by Mladen Turk <mt...@apache.org>.
On 03/19/2012 03:57 PM, Mark Thomas wrote:
> On 19/03/2012 14:55, Mark Thomas wrote:
>> On 19/03/2012 14:48, Mladen Turk wrote:
>>> Hi,
>>>
>>> I plan to tag 1.2.34 tomorrow cause we have one regression
>>> and few long lasting bugs fixed.
>>>
>>> I'd appreciate if you can check the httpd builds from trunk
>>> since I concentrated mainly on IIS.
>>>
>>> BTW, should we remove/revoke 1.2.33 or just go with 1.2.34?
>>> IMHO 1.2.33 is unusable, so that's a valid reason.
>>
>> 1.2.33 has been released so go with 1.2.34
>
> Misunderstood the question. Lets just get 1.2.34 out there.
>
OK.
> Might be worth an email to announce@ now for the folks not following the
> users list.
>
Do you have any template for that?
Cheers
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Release JK 1.2.34
Posted by Mark Thomas <ma...@apache.org>.
On 19/03/2012 14:55, Mark Thomas wrote:
> On 19/03/2012 14:48, Mladen Turk wrote:
>> Hi,
>>
>> I plan to tag 1.2.34 tomorrow cause we have one regression
>> and few long lasting bugs fixed.
>>
>> I'd appreciate if you can check the httpd builds from trunk
>> since I concentrated mainly on IIS.
>>
>> BTW, should we remove/revoke 1.2.33 or just go with 1.2.34?
>> IMHO 1.2.33 is unusable, so that's a valid reason.
>
> 1.2.33 has been released so go with 1.2.34
Misunderstood the question. Lets just get 1.2.34 out there.
Might be worth an email to announce@ now for the folks not following the
users list.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Release JK 1.2.34
Posted by Mark Thomas <ma...@apache.org>.
On 19/03/2012 14:48, Mladen Turk wrote:
> Hi,
>
> I plan to tag 1.2.34 tomorrow cause we have one regression
> and few long lasting bugs fixed.
>
> I'd appreciate if you can check the httpd builds from trunk
> since I concentrated mainly on IIS.
>
> BTW, should we remove/revoke 1.2.33 or just go with 1.2.34?
> IMHO 1.2.33 is unusable, so that's a valid reason.
1.2.33 has been released so go with 1.2.34
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Release JK 1.2.34
Posted by Christopher Schultz <ch...@christopherschultz.net>.
Mladen,
On 3/19/12 10:48 AM, Mladen Turk wrote:
> I'd appreciate if you can check the httpd builds from trunk
> since I concentrated mainly on IIS.
As mentioned in BZ, trunk from today builds and works remarkably better
than 1.2.33 in my environment: no crashes, warnings, etc. I've got it
running in our development environment right now. I'll let you know if
in a few hours anything odd happens.
Thanks for the quick fixes.
-chris