On Mon, Oct 31, 2016 at 3:24 PM, Sven Meier <[email protected]> wrote: > Hi, > > IMHO 8.x is ready to be promoted to final, as I don't see any additional > major changes for it. > > I'll be upgrading a big application from 6.x soon, and I'd love to target > 8.x instead of 7.x >
It would be good if you can try to upgrade before we release the final. This way you can find bugs/improvements before the "API break freeze". I've migrated my current application to 8.0.0-M1 in a branch and I keep it up-to-date to be able to test 8.x milestones. As soon as you are ready and there are no major issues found we could release 8.0.0 final. > > Sven > > > Am 31.10.2016 um 14:41 schrieb Martin Grigorov: > >> Hi, >> >> What other improvements do we need in 8.x/master before promoting it to >> 8.0.0 final ? >> >> At https://cwiki.apache.org/confluence/display/WICKET/Ideas+ >> for+Wicket+8.0 >> we still have: >> >> - new DateTime APIs for wicket-datetime *WICKET-6105 >> <https://issues.apache.org/jira/browse/WICKET-6105>* - I'll give this one >> more try but the problem is that I don't believe this is the proper way >> and >> this demotivates me. >> If someone else wants to give it a try - please assign it to yourself! >> >> - Better SEO for stateful pages - the only way I see this is by using >> ServiceWorker to add the pageId as a request header to all requests >> (normal >> & Ajax) >> >> >> Recently I wondered whether Redux.js could be in use for Wicket. >> I don't have much experience with it, but both React and AngularJs >> communities use it to manage the state for their components. >> There are some Java impls, even a standard is coming: >> https://github.com/jvm-redux/jvm-redux-api >> >> What else ? >> >> Martin Grigorov >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> >
