We are a little bit confused about the future directions of the wicket project. We startet switching from wicket 1.x to 2.0 in june 2006 and are working with wicket 2 now for more then 10 months. One year ago it seemed that wicket 2.0 (with generics and new constructor) will be the future and was designed to overcome some problems that were within the design of wicket 1.x. In other words, wicket 2.0 will become the new and better wicket with the 1.x problems solved and 1.x will be put in a maintenace only state when wicket 2.0 is ready. Now it sees that the main development is like "implementing new features in 2.0 and backport them to 1.x" and if the process of backpüorting becomes too expensive, 2.0 has to be modified to make it easier (go back to old constructor, degenerify etc.). Some postings on the developer list sound like "let's drop the whole 2.0 thing and concnetrat on 1.3, 1.4 and so on. Can you help us to see a clear roadmap for wicket? What verson should we concentrate on in further application development? Stefan Lindner
<<winmail.dat>>
------------------------------------------------------------------------- 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
