On 16/03/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
On 3/16/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
> So please clarify: what is the intended life time of 1.3.x once
> 1.4.x is created? Currently in Wicket 1.2.x we only checkin
> critical fixes, it is a maintenance branch. Do you intend to turn
> 1.3.x into a maintenance branch once 1.4.x is created? In this
> case I'm happy with the roadmap.
In my opinion we should treat 1.3.x the same as 1.2.x currently. That
is bug fixes only, possibly some backports, but those should be the
exception, not the rule. However the first weeks of a released 1.3 may
be slightly different (no fork to 1.4.x until 1.3.1). But I would
recommend forking earlier than we did with 1.2.
There's a thread about Post-1.2 from 13 months ago that's very familiar. :-)
My preference would be to get the 1.3 release out, wait for a few days
(no more than a week) then branch and start moving to 1.4 if no major
issues appear. I'm convinced 1.3 will take much longer than hoped to
get out, for various reasons, technical, 'political' & practical, so I
don't think we should commit to no forking until a second release - I
think that would restrict things too much.
In general though, I think we should try harder to limit 1.3 to
bug-fixes than was done with 1.2 and focus on trying to do more rapid
releases of 1.4.x. Basically, my vote would be that once Wicket 1.3's
out, we stop development for JDK/JRE 1.4.x.
/Gwyn
--
Download Wicket 1.2.5 now! - http://wicketframework.org
