On 2/6/07, Jon Steelman <[EMAIL PROTECTED]> wrote:
I understand that 3.x hasn't been started yet, but I'm curious what - if anything - is being held off for 3.x instead of being done in 2.x?
We have nothing concrete at this time. I think the main thing we (Igor) is thinking about for 3.0 is to change the render process from being stream driven to component driven. Or something like that. The main reason to even talk about 3.x is that at some point we want to draw a line and say 'this is for 2.0 and this is for some future'. 2.0 is officially our current development version, though as everyone of the core team is building production systems in 1.3, that version gets a bit more attention :) The main reason to limit what we'll do for 2.0 is that we want to have a release out this year, and that we are writing Wicket In Action (long overdue but also planned for this year) against that version.
For example, if 2.x is allowed to and will have for example API changes, what type of change qualifies waiting for 3.x versus 2.x?
You are right in this, and what is called 3.x now may just as well be put in 2.1. 3.x is hypothetical at this point, and personally I hope it stays hypothetical for a while as we have enough stuff to care about :) Eelco
