Not binding. But still have an oppion:)
Id say go for 2.0 if it includes generics, it'll leave space for
maintenance releases on the 1.3 branch. And clearly signal that
something big has happend, namely that you now need to use java 1.5
my thoughts..
regards Nino
Martijn Dashorst wrote:
All,
With 1.3.2 out the door we should start planning our next release.
We have agreed upon doing milestone releases to give our current users
a quick and easy way to play with the new features, such as generics.
Between those milestones we don't promise API stability, so if
generics don't work or need some tweaking we are free to change that.
But first things first:
1 - wicket 1.4 or 2.0 (for now I'll refer to Wicket Next Generation (WNG)?
2 - are we going to timebox the milestones, or plan on features added?
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.
2. Time box or feature box milestones
I think feature box is the way to go.
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
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:
Martijn
--
-Wicket for love
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684
