because we are dropping 2.0 as un upgrade path
there are numerous reasons to put every feature of 2.0 in 1.3
first not to screw the people that do use 2.0 twice
that we drop it and that they have to backport it with nothing not only the
constructor change but also the rest
(and when they have done that going to 1.3 and we release 1.4 they have to
undo there undo's again!)
secondly if we release that fast as it is now proposed then we go instead of
having
2 active branches (1.3 and 2.0) and one maintenance (1.2) to
1 active branche (1.5) and 2 to maintain (1.3 and 1.4)
why are we wanting that? I don't i will not fix over 4 branches gain. Thats
the whole point of dropping 2.0
thirdly if we are releasing that quickly we pretty much say to every
1.3user do upgrade also to
1.4
(we really can't do that thats why we have point 2) But if that is the case
then why have 1.3? What is that
1.3 release? Its just a quickly intermediate build.
I could go on for some more time and point out a few extra points why i
really don't like the current proposal.
Its just more work for everybody in the long run, for our users and for our
selfs.
johan
On 3/8/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
* Igor Vaynberg:
> THIS VOTE NEEDS TO GO ON USER LIST
Please Igor and Johan,
Many important things are currently discussed, it becomes very
confusing for both the developers and the users to follow. Can we
slow down the rate at which new proposals are raised, and at least
agree on wicket-dev before proposing something on wicket-user? I
don't think it's a good idea to ask users opinion when we
don't have a clear understanding for this ourselves.
Of course we will backport this feature if a majority of people
think it's good, but maybe not *right now*. We have enough things
to deal with ATM. Get a release out first, then merge the
features we want from trunk *progressively*. There's no hurry.
And Johan, what do you call 1.3 by the way? Is it the release
that we are all expecting since months? In this case I follow
AlMaw's opinion, please let the dust settle and do it in a few
weeks.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
