1.4 isn't just 1.3+java5 features.
In my eyes it will be trunk for at least 4-6 months after 1.3 is released.
We also could just call that 2.0 and do java5 and other things that come
along
and what we planned for 2.x/3.0
johan
On 3/16/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
Hi there,
As a vote is not appropriate for discussing, I'm creating another
thread, and I'd love to be able to discuss those issues with you
prior to voting. You mentioned in your proposal that you intend
to fork 1.3.x to 1.4.x for JDK 1.5 features. And you also state
precisely that we'll have to maintain two branches at the same
time.
I'm against that, and it's not matching our previous discussions.
We have agreed several times in the past weeks that we don't want
to maintain multiple branches.
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.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
