I'm ok with trying 7.0.40. If it takes more then a week to resolve any
potential regressions we can always switch back to 7.0.39 quickly.
Alternatively, we can also port back specific fixes from 7.0.40 to our
7.0.39.

Jarek

On Thu, May 16, 2013 at 12:09 AM, Forrest Xia <[email protected]> wrote:
> 7.0.40 may bring in unexpected tck issue. We just hited and fixed a tck
> regression brought by 7.0.39 upgrade. Since now the tck is in good shape, I
> would prefer to make 3.0.1 release based on the validated 7.0.39 fork first.
> thoughts?
>
>
> On Thu, May 16, 2013 at 11:37 AM, Kevan Miller <[email protected]>
> wrote:
>>
>>
>> On May 12, 2013, at 10:29 PM, Forrest Xia <[email protected]> wrote:
>>
>> > Tomcat fork 7.0.39.1 is out, shall we start release of 3.0.1? Anything
>> > more to add, please comment it on, or I will start the release process
>> > around May 16.
>>
>> Unless I'm mistaken, looks like we'll need to move up to 7.0.40.
>>
>> --kevan
>
>
>
>
> --
> Thanks!
>
> Regards, Forrest

Reply via email to