Its not that revolutionairy. For example if 1.4 was just 1.3+generics then if your project like vocus thats already on 1.5 it would be a drop in replacement. So api and 'feature' wise not much has happend then, only easy of development (for most not all are fans ;))
On 3/14/08, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > On 3/14/08, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > is the next release an evolution or revolution? :) i think first we > > need to make a list of all major things we want to go into it, and > > then decide. > > I think it counts as revolutionary: abandoning Java 1.4 is > revolutionary I think. > > > > 2 - are we going to timebox the milestones, or plan on features added? > > > > personally i think we should come up with a list of all the features > > we want, throw them into a backlog, and timebox it. > > See the wishlist: http://cwiki.apache.org/WICKET/wicket-14-wish-list.html > > > > 3 - how many milestones do we plan? > > id like 6. 1-4 dev, 5-6 stabalizaton. we were never able to get away > > with just one beta release before, most bugs are found after we put > > out the first beta...so i dont expect a lot of bugs to be found until > > the last dev milestone goes out. > > Fine with me. > > > > 4 - which features go into each milestone? > > what are the features? :) > > :D > > http://cwiki.apache.org/WICKET/wicket-14-wish-list.html > > Martijn > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.1 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.1 >
