Then I'd suggest renaming Wicket 1.6 to Wicket 2.0, for the psychological
impact, and to state clearly that this is a break in Wicket development.
As for Java 1.5 vs 1.6, companies upgraded to 1.5 because it came with a
huge lot of new features and improvements that their architects felt could
that would be weird.
if wicket 1.3 to wicket 1.4 would be just a .1 increase because of java 4 to
5
but because of java 6 we suddenly have to call it wicket 2.0?
purely looking at the java version used wicket 1.3 to 1.4 is a way bigger
leap then wicket 1.4 to 1.5
(looking at the changes wicket
Hi,
that would be weird.
I think the current situation with a deprecated release wicket 2.0 is also
weird. Perhaps the wicket developers should jump over the 2.0 border and
create a 3.0/2.5 (whatever 2.0 :)) release instead of a 1.5 ?
Best Regards,
Ilja Pavkovic
if wicket 1.3 to
