We have released 3 bug fixes to 1.5.x and it seems like it is more
stable now. Stuff for wicket.next is piling up, so I propose we start
our wicket-6.x.y work, using semantic versioning. Since Wicket 6 will
be a breaker API wise, we can just stick with trunk for new
development, and move maintenance for 1.5.x to a branch.

WDYT?

Martijn

Reply via email to