Hey Jochen, I see we might not be fully done with the 5.4.1 release yet but
would it be ok to branch out 5.4.x? Looks like I got some free time in my
hands in the coming weeks so I can set up 5.5 for the master and start the
work on migrating jpa-transactions.

Kalle

On Thu, Mar 24, 2016 at 2:59 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:

> On Wed, 23 Mar 2016 19:12:30 -0300, Kalle Korhonen <
> kalle.o.korho...@gmail.com> wrote:
>
> Now that 5.4.1 is out, it might be a good time to move ahead with this
>> plan, create a branch for 5.4.x and reserve the master for 5.5 development
>> with Java 8. I'm much more concerned with degradation of the test suite
>> (since the tests aren't being run until we can upgrade Selenium) than
>> merging/backporting everything from 5.5 to 5.4.
>>
>
> +1
>
>
>> Kalle
>>
>> On Tue, Feb 2, 2016 at 4:28 AM, Bob Harner <bobhar...@gmail.com> wrote:
>>
>> I'd say just proceed. I don't think a vote is required, especially since
>>> there has been more than a month of discussion and no real objections.
>>> On Feb 2, 2016 6:31 AM, "Jochen Kemnade" <jochen.kemn...@eddyson.de>
>>> wrote:
>>>
>>> > I'm +1 with 5.4 being maintained for jre 1.6 or 1.7 and Tapestry 5.5
>>> being
>>> >> for jre 1.8 users
>>> >>
>>> >
>>> > Of course, that means that someone will need to maintain it. I'm not
>>> > overly confident that we are going to be able to maintain two release
>>> > branches.
>>> >
>>> > So, what do we do now? Do we need a vote?
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
>>> > For additional commands, e-mail: dev-h...@tapestry.apache.org
>>> >
>>> >
>>>
>>>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: dev-h...@tapestry.apache.org
>
>

Reply via email to