Agree: rename master -> main. And archiving/deleting older branches is good. We have the tags available as reference points if any emergency release needs to be created for an ‘unmaintained’ release series.
Matt > On Nov 2, 2026, at 2:00 AM, Emond Papegaaij <[email protected]> wrote: > > Agreed. Master becomes main (version 12), wicket-11.x gets its own > branch and the old branches are renamed to archived/wicket-xx. > > I also agree with Maxim. We should probably just delete any feature > branch that hasn't had any commits in the past 2 years. > > Emond > > Op ma 2 nov 2026 om 01:57 schreef Maxim Solodovnik <[email protected]>: >> >> I would also propose to clean-up at least some of other 80+ branches :) >> >> from mobile (sorry for typos ;) >> >> >> On Mon, Nov 2, 2026, 03:26 Martijn Dashorst <[email protected]> >> wrote: >> >>> Let's make a wicket-11.x branch >>> >>> Also let's move all non-LTS and older branches to: >>> >>> archived/wicket-6.x >>> archived/wicket-7.x >>> ... >>> >>> Probably we should consider renaming master to either main or >>> wicket-12.x (my preference would be main, because otherwise we are >>> going to keep renaming the default branch) >>> >>> I'm going to modify the readme for wicket 11 to get a better >>> appropriate header, so it matches what is on that branch. >>> >>> Martijn >>>
