We're starting a new project and thinking about using Wicket for presentation layer.
One concern is about backwards compatibility and support. I understand 1.5 is coming and in not fully backwards compatible. The concerns: If we start with wicket 1.4.8, a few years from now all development is done to 1.5.x and no one cares about boring old 1.4 anymore. No bugs will get fixed anymore and when Internet Explorer 10 is released, page markup, javascript, and AJAX features stop working. We need to do an expensive wicket 1.4->1.5 port for our application. Or, we start with wicket 1.5. It gets GA released whenever, and goes through a few years of being buggy and unmature. What's the best option to take now? How big are the "backwards incompatible changes" planned for 1.5? What's the schedule for 1.5? How mature are wicket x.0 releases usually? What's the track record on updating older releases? -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-vendor-lockin-and-backwards-compatibility-1-4-1-5-tp2226109p2226109.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
