Hi,
On Fri, Jan 24, 2014 at 1:39 PM, Martin Grigorov <[email protected]>wrote: > On Fri, Jan 24, 2014 at 2:30 PM, Martijn Dashorst < > [email protected]> wrote: > > > I'm hoping to finalise wicket 7 somewhere before the summer. But I can't > > guarantee that. > > > > My reasoning: > > - I expect Wicket 8 to be Java 8 based (lambda expressions and the new > > date/time APIs would make good additions to Wicket) > > - Wicket 8/Java 8 development should start when Java 8 is out and has > good > > availability in open source containers (wildfly already supports java 8) > > - we have to get comfortable with Java 8 idioms to make the correct > > adjustments to Wicket, and this takes time > > - it takes a couple of months (2-5 ish) before we can finalise wicket 7 > > (solve issues, stabilise APIs) > > - I'd like to see the experimental modules we built in Wicket 6 to get > > some adoption and give us some feedback before we make wicket 7 final. > This > > way we can fix API issues in the Wicket 7 modules (because semver). > > > > From a personal/commercial perspective it is best when we (Topicus) can > > integrate Wicket 7 before the summer time so we can stabilise our apps > > prior to getting hammered by oodles of users. > > > > Early feedback is welcome even from Topicus! ;) > That was I idea when I asked the question. I would not mind running on release candidates as far as the functionality I use is stable and I get proper feedback reaction from core developers... and the price I have to pay on time for that is not to high.
