correct. the commitment we make is: new features go into current major version we maintain major.version-1 - which means backporting bug fixes we support major.version-2 - which means we backport security releated fixes
-igor On Sat, Apr 27, 2013 at 1:07 AM, Martin Grigorov <mgrigo...@apache.org> wrote: > On Sat, Apr 27, 2013 at 9:56 AM, Sven Meier <s...@meiers.net> wrote: > >> [x] Yes, start working on Wicket 7. >> >> When are we going to declare a feature freeze for Wicket 1.5.x? >> > > Lately I'm backporting only bug fixes to 1.5.x. > New features go only in 6.x. > It is not a problem for me to release 1.5.x for some more months. The > release script makes this really easy. > I think we can freeze it for security related bug fixes only once Wicket > 7.0.0 is released. > > >> >> Sven >> >> >> On 04/25/2013 03:15 PM, Martin Grigorov wrote: >> >>> Hi, >>> >>> I think it is time to start the work for Wicket 7.0. >>> At >>> https://cwiki.apache.org/**confluence/x/D4flAQ<https://cwiki.apache.org/confluence/x/D4flAQ>you >>> may see the proposed >>> roadmap. >>> >>> The entries are extracted from >>> https://cwiki.apache.org/**confluence/x/rwjVAQ(Ideas<https://cwiki.apache.org/confluence/x/rwjVAQ(Ideas>for >>> Wicket 7) and >>> >>> currently contains only what I find interesting to >>> me and can implement by myself. >>> If you want some of the other ideas included then add it and assign it to >>> yourself. >>> >>> The change that will cause API breaks is "Use Java 7 + add generics to >>> o.a.w.Component and descendants" >>> >>> Vote options: >>> [ ] Yes, start work on Wicket 7 with the proposed roadmap >>> [ ] No, it is too soon to mandate Java 7/Servlet 3.0 >>> [ ] No, the suggested improvements are not enough for a new major version >>> >>> >> > > > -- > Martin Grigorov > Wicket Training & Consulting > http://jWeekend.com <http://jweekend.com/>
