> > 3 - how many milestones do we plan? > 4 - which features go into each milestone? > > 1: Wicket 1.4 or 2.0? > > If I remember correctly we decided on 2.0 with a small margin.
1.4 or 2.0 depends on me how fast and and how big change the next release will bring Is it just generics and some nice features and not even big api breaks? Is then 2.0 really already what we want to call it? I dont know if Matej want to do a refactor of the url encoding and juergen (or who ever) wants to do an overhaul of the markup parsing? If that is the case then 2.0 is fine by me. (then the final will also take longer) > > > 2. Time box or feature box milestones > > I think feature box is the way to go. We can plan some and yes timebox is a bit difficult i think. I cant promise that i can do stuff at any time and how much time i can spent on it. I guess thats the case for the most of us. I will start with generics as soon as i can, maybe this weekend. But when are we going to branch? When is head not 1.3.x anymore? > > > 3: How many milestones? > > I suggest 5 milestone releases: > WNG-M1 - WNG-M4 : add new features, fix bugs in previous milestone > WNG-M5 : API freeze, move to release > We should focus on adding 2-3 bigger features per milestone, and > reserve other features for WNG.1 something like that if fine but.. > > > 4: Which features in each milestone? > > Our planning should be committed to a Wiki document or in JIRA, but > for discussion sake, I'll post the milestone list here: > > M1: generics only > M2: > M3: > M4: > M5: I dont know if i can really say that milestone has that feature. Its really more a thing who as the time for what at what time. And some features just cost time. Now i think about it . Maybe a timebox is better lets say every 1.5 month or 2 months And then decide with all of us what features are really should be in the final and then plan 1 milestone ahead. Then maybe the time constain will push us a bit (just as when Frank says lets do 1.3.2 this weekend, suddenly loads of bugs where fixed :) ) But anyway if we do a timebox or just feature planning Do it 1 milestone ahead. I dont think we can really plan M4 already.. johan johan
