> [...] Also new > releases need to be backward compatible and I'm not sure we want a new > release every 3 months with a lot of possibly disrupting changes. > This might accelerate Wicket's progress but hamper companies relying on > wicket being stable and backward compatible. IMHO this would be rather > irritating for users. > Something stops working, and you need to find out why, report the issue, > and wait for a new release (or a hot fix release)
This. Wicket already is hard to sell. Breaking backwards compatibility (unless unavoidable because of security concerns) is terrible. Wicket applications are usually big, because that is what Wicket was built for. The amount of Wicket code will likely make migrations expensive. Yesterday I spent an hour trying to figure out why 1 of our CSP tests fell over after upgrading to the latest version. It was because of recent CSP handling changes. Kind regards, Johan
