I am completely agains a quick 1.4 generics only real release. We will create a milestone 1 build of 1.4 with generics and maybe some small other stuff that would normally break 1.3 (i have a 1 or 2 bugs that do break api when i fix that so dont know if we can do that in 1.3)
But doing a 1.4 release so quickly with only generics means for me merging of 3 branches. Or can we at the moment we release 1.4 completely drop 1.3? Dont think so. So thats a -100 for me i am not going to merge over 3 branches. I am all for releases as 1.3 when we release 1 major version the previous one is quite stable and dead in maintenance/development. Johan On 3/15/08, Jonathan Locke <[EMAIL PROTECTED]> wrote: > > > i would prefer a very fast 1.4 release with only generics support while we > do this planning for a 1.5. since we already did this once, i would imagine > it could be done again in a month or two with a full release that makes a > lot of people happy and breaks practically nothing. that would give us > plenty of time to plan in the meantime. > > i have permission here at work to open source some of our mobile components > and would like to add some base-level support for WML and some > infrastructure that supports mobile devices in general to the next > generation (whether it's 1.4 or 1.5). whether this ought to go in core or > somewhere else is up for debate. it's surely lower priority than some other > features, but i thought i'd throw it in there. > > > 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 > > > > -- > > 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 > > > > > > -- > View this message in context: > http://www.nabble.com/Planning-Wicket-Next-Generation-tp16046194p16062416.html > Sent from the Wicket - Dev mailing list archive at Nabble.com. > >
