> i came over from another framework to wicket because i didnt like the > api change with every release there and liked the way wicket does things. > > first i was not sure which version of wicket to use and read the mailing > list and found out, that 2.0 suits best to me. after starting 2 bigger > projects with 2.0 which have deadline in a few weeks, i would appreciate > any (fast ;-)) decision of you regarding the future of 2.0 as for me it > doesn't make sense to ride a dying horse and probably have to backport > my 2.0 components to 1.3 (coz of the missing generics support and > constructor change) and later in a few weeks port them to new 1.5 (or > 1.6/1.7...) to be up to date and use them in my next projects.
As far as I am concerned, we could make a decision this week, and I can reserve this weekend to work on porting and preparing and - though it may take a while before we have actual releases - I hope we'll be able to get something workable in SVN soon (like by next week). Regards, Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
