I disagree with this and i will always vote this down. 1.4 will not be just a 1.3 with generics. If we do that then i will tell everybody now that i will not merge over 3 branches.
Also 1.4.1 with suddenly api breaks?? 1.4.x should be api stable. So all the new features then will be 1.5. So then we have 3 branches then. So we just should do something else. After 1.3 make a timeframe let say july 2008 we will try to release 1.4 and then try to get things in what we can. Johan On 12/15/07, Gwyn Evans <[EMAIL PROTECTED]> wrote: > On 15/12/2007, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > A general remark about this list is that I also think this actually > > should be 1.4.1. We agreed a long time ago that 1.4 would be only the > > last missing parts of 2.0 (Java 5 related things, most notably > > generics). Like I predicted back then, it is taking us a long time to > > reach 1.3, and we should have the discipline of sticking to what we > > promised way back: 1.4(.0) is about the last 2.0 ports, and after we > > have a good 1.4.0 final, we can start on new features again. > > Totally agree - I think I saw a comment on users@ from Johan or Igor > to the effect that we hadn't had a discussion as to what 1.4 was, > whereas my recollection is that we certainly stated what 1.4.0 was to > be, i.e. as above. > > Personally, I'd be very against anything going into 1.4 that wasn't > either a bug-fix found in 1.3.x or directly related to a 'missing' 2.0 > feature. > > /Gwyn > -- > Download Wicket 1.3.0-rc2 now! - http://wicketframework.org >
