1.3: no API breaks unless absolutely necessary, no new features (remember: support stops for 1.3!) 1.4: generics only release. 1.5/2.0: new features, api breaks etc.
So 1.5/2.0 according to my recollection of the meanings of our releases. Martijn On 3/25/08, Timo Rantalaiho <[EMAIL PROTECTED]> wrote: > Devs, > > Have you had time to think about this: > > > https://issues.apache.org/jira/browse/WICKET-1312 > > > Judging from the interest on this list and in issue > comments, there is demand for an event mechanism in Wicket. > Surely it needs to be developed further from this patch, but > you've got to start from somewhere. (And this is essentially > something that we've used for a few months now with good > results.) > > Would it be a good idea to include the current patch version > already in 1.3.3 (and thus in 1.4), or better let it brew > more? > > Pros: > > - some kind of event mechanism available for 1.3 / 1.4 users > > - possibility to gather feedback on the mechanism to be able > to make a better one in 1.5 without worrying about > breaking the API > > Cons: > > - more new code to maintain in 1.3 / 1.4 branch > > - if the API gets deprecated and/or changed dramatically in > 1.5, it makes sad users anyway (even if there is > "permission" to break the API) > > > Best wishes, > Timo > > -- > Timo Rantalaiho > Reaktor Innovations Oy <URL: http://www.ri.fi/ > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.2 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.2
