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); 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 when I close the issue; that way it'll show in the release
notes for both 5.3 and 5.4.
--
Mit freundlichen Grüßen / Regards
Michael Wyraz
evermind GmbH
Schorlemmerstraße 1
04155 Leipzig
Tel.: +49 (0)341-25 39 66 - 0
Fax: +49 (0)341-25 39 66 - 1
Funk: +49 (0)177-73 00 00 3
E-Mail: michael.wy...@evermind.de
HRB: 21586
Amtsgericht Leipzig
Geschäftsführer:
Christoph Klemm
Thomas Grünert
Michael Wyraz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
