I'm seeing some minor bugs fixed in master (5.4); I'm sure our users
would like to see those back-ported to 5.3. Now that we have Git, it
is generally super-easy to do, just a matter of using the git
cherry-pick command.
When I've been back porting, I identify both releases as the fix
releases wh
Thanks. It is great that 5.3 will benefit from it since upgrading all
projects from one tapestry version to the next is always lot of
(testing) work.
So should developers now always submit patches for 5.4 and can expect
them to be added to 5.3?
I'm seeing some minor bugs fixed in master (5.4)
Anyone?
On Tue, May 22, 2012 at 6:43 PM, Dimitris Zenios
wrote:
> Hi guys i think there is a bug in tapestry-jpa and value encoder
>
> In a discussion i was reading, Howard changed valueEncoder of
> tapestry-hibernate to return null in toClient if the id of the object
> was null.That was use full
