Hi Tobias, I think this is because some preliminary investigations (or work) have been done while wicket-8 was still master (I think it was about JDK-9) So logically, wicket-9.x could or should be merged into master...
But, the other question could also be, why do we have master at all? In Wicket jQuery UI, I was working on wicket8.x branch already and I will remove master soon so I will only have wicket6.x, wicket7.x (prev master), wicket8.x, and wicket9.x (soon). It make more sense to me and there is no - potentially - weird rebase/merge to do to master after each major version. Best regards, Sebastien. On Thu, May 24, 2018 at 1:23 PM, Tobias Soloschenko < [email protected]> wrote: > Hey guys, > > maybe I missed something, but why do we have master and wicket-9.x? > > I thought the latest version is master and all others are wicket-x.x. > > kind regards > > Tobias >
