I agree with Martijn on almost everything he said. We deeply need a predictable release policy to keep Wicket alive and kicking and attractive. Still have some doubts about the 3 months timeframe,which it might be too ambitious and too "aggressive" for our user base which is mainly enterprise-oriented. I also think that, like it or not, we might also need some kind of "API break" policy in order not to stress users too much. But on this last point I agree we all don't want to break API for the sake of it and we might proceed through a vote...
In the meantime, let's not forget we have Wicket 11 waiting for rolling out 😊, we should also decide about a possible timeframe for it's release. "Do something, anything!", Mario Draghi :-) On Mon, 24 Aug 2026, 16:17 Martijn Dashorst, <[email protected]> wrote: > I've read the thread and here are my thoughts. > > The point is not to break compatibility every 3 months. The point is that > we stop promising that we won't. > > ... Andrea Del Bene. Apache Wicket committer.
