On 10/03/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > a) focus on stabilizing 1.3 first, meanwhile keep supporting 2.0 > (though only for bugfixes). 1.4 will be the release with backports of > the currently missing 2.0 features, and 1.5 will be 1.4 + the Java 5 > features (including generics). > > b) as a) but rather than developing 1.3 up to a final release, freeze > asap (only fix bugs) and start on 1.4 > > c) put all backports except for the Java 5 features in 1.3 after the > beta1 release (which we agreed upon doing this weekend). 1.4 will be > for the Java 5 features, and the branch should be started as soon as > 1.3 is feature complete.
Hi, I've kept quiet, as I've not had a chance to actually get into 2.0, so have no personal view on rollback, but I'm certainly not going to go against the experiences of the committers who do have to deal with the multiple branches. My preferences would be (c), for the same reasons you state in your other email. Regarding the "beta" release, I think we must do the release ASAP, if for no other reason than to work through the stages of an Apache release, although I'm not sure what the best designation is - personally I'd consider calling it a "checkpoint" release, but that's another matter! /Gwyn ------------------------------------------------------------------------- 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