> backport everything new and useful into 1.4 (or seems like even 1.3 since > you guys got such itchy fingers).
Those itchy fingers are easily explained: we'd like to get in those 'missing' features in asap so that we don't have to worry about backporting them in the future! Furthermore, don't play such an innocent kid, because you've been guilty of applying or at least encouraging quite a few ajax and header contribution backports yourself! > at that point we will decide whether or > not we will make 1.3 or 1.4 the last java1.4 version, and from then on move > on to java5 with the older version being in _maintenance_ mode. We have to take some responsibility here don't we? If we decide to reverse the constructor change, that doesn't mean we just drop the whole thing right away. As you have read in the thread so far, people /are/ using those generics, so we /should/ provide a proper upgrade path. And I mean very soon, not just in some distant future. So, yes, we have to either keep 2.0 alive for bug fixes and stuff, or we have to provide a version that is as close to 1.3 as possible, but with generics/ java 5 support. 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
