I like your plan actually. Generally, I'd like to make it better and easier to use Tapestry as a REST backend (as related to the recent discussions on the user list) but I really don't want to bring in another dependency and in all honesty, most of the integrations to third-party libraries are much better of at Github than at Apache.
Kalle On Tue, Dec 29, 2015 at 7:41 AM, Jochen Kemnade <jochen.kemn...@eddyson.de> wrote: > Hi, > > I'd like to hear some opinions about how we should proceed with the > Tapestry development. > > Which are the things we want to do for 5.5? > What are the things we want to do for 5.4.x? > Do we want to create a 5.4 branch and start progress on 5.5 right away? > > I'll go ahead and open the discussion with this proposal: > > I'd like to start working toward 5.5 pretty soon and I'd like it to take > much less time than 5.4 did. > For 5.5, I'd like to require Java 8, update some libraries, maybe add > support for Geb tests, and remove some deprecated code. That's basically it. > As Java 8 and some library updates can't be done for 5.4.x, I'd create a > 5.4 branch right now and do the updates in master. > I'd prefer if we concentrated on the 5.5 release and only backport bug > fixes to the 5.4 branch. I hope we can get 5.5.0 out soon so we won't need > to do too many 5.4.x releases. > > Now let's hear some other opinions. :-) > > Jochen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org > For additional commands, e-mail: dev-h...@tapestry.apache.org > >
