If users can, they should try to migrate. If users have severe bugs in 1.2.x and they can't upgrade, we'll patch it, but it is something that first have to be voted for. For 1.3, see migration here: http://cwiki.apache.org/WICKET/migrate-13.html. For most people it should be a pretty easy fix, and the extra features are imo worth a little bit of trouble. That said, we do understand that not everyone is in the position to upgrade to a version that isn't released yet and has backward compat breaks, so if a fix is really important for you, please start a vote.
Eelco On 1/22/07, Sean Sullivan <[EMAIL PROTECTED]> wrote:
I understand that Wicket 1.2.x is in maintenance mode. However, Wicket 1.2.4is the only version that has been deemed a production-ready release. Should users continue using Wicket 1.2.4 or should they move to the unreleased Wicket 1.3 codebase? Sean On 1/22/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > yes thats the one > > and no, afaik it will not. if you want it you can start a vote to have it > included. just keep in mind it is already very time consuming for us to > work > on 2 branches, not to mentioned 3 > > -igor > >
