It would seem to me, that through this dropping of constructor
change, and abandoning the 2.0 trunk/ ... There needs to be a really
nice and easy path to changing to the 1.3 or 1.4 branch, whatever the
case may be, and it needs to be clear. I have a feeling the 2.0
users are those most under the Wicket reality distortion field, and
the biggest cheerleaders, so making sure they don't feel abandoned is
important.
From what I'm hearing, the model change is the biggest item on the
agenda, and second is Java5. It seems like 1.3 should have the model
change, and 1.4 should have Java5. But I would hope that 2.0
continues to receive bugfixes on an as needed basis, or you risk
losing your fanatics because they have nowhere to go.
Andrew
On Mar 8, 2007, at 9:59 AM, Eelco Hillenius wrote:
why put a beta out if a huge api break is coming??? i will change
my vote to
-1 on releasing 1.3beta if we decide to fold the model refactor
into it.
I don't find that kind of power play to be very constructive,
especially not because you are largely responsible for the 2.0
controversy (after being the greatest advocate for the change in the
first place, and now the greatest advocate of reverting it). It's
simple, if you want dropping 2.0 to happen you have to go through some
pain too. If 2.0 stays, the models don't have to go in 1.3.
Eelco
