I agree with Leonardo totally. Just because you have a 2.0 branch does
not mean that you drop support for 1.1. It simply means that things
which cannot be made 1.1 compatible continue to migrate and that the
stuff which is already in place, embraces any emerging standards.
Furthermore, it gives Tomahawk users a much clearer upgrade path into
the new technologies. Trinidad, for instance, has had a 1.2 branch for
a few months and we are totally seeing enhancements going into both
branches. Things go into 1.2 as the exception, not the rule.
I fully support making sure that 1.1 continues to move ahead because 1.1
is MyFace's largest community of users. But PREVENTING projects from
moving to the new technology only hurts those renderkits and helps
no-one.... One of the key issues with open source is that developers
work on what they want/need to work on. If people in the community
continue to restrict developers from supporting the new standards for a
renderkit, the renderkit will loose developers and support. Instead of
having active development in a project with a little more emphasis on
the later standards, you'll end up with no development at all.
Just my 2 cents.
Scott
Leonardo Uribe wrote:
On Mon, Mar 3, 2008 at 4:58 PM, simon <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
The list of components is fine. And I very much appreciate all
your work
on this and the tomahawk bugs you've been fixing recently.
However at the risk of sounding like a broken record, I would like to
point out that AFAIK there has still been no vote on whether to have a
tomahawk 2.0 at all. And I would vote -1 on such a thing; abandoning
tomahawk users on JSF1.1 would be bad, and the community is just
not big
enough to support two parallel tomahawk branches. The fact that
you are
about the only person to commit to tomahawk in the last month should
make that obvious. The minor benefits of a JSF1.2-specific tomahawk
branch are far outweighed by the pain.
I have a different opinion about this. Sooner or later we have to
upgrade this lib (I think better sooner than later).
The component generator does the big part of the update (write
component and tag classes),
only minor changes on the renderers was done to make all examples work
(the big part
of the work is on build module). Move changes from one branch to
another should be an
easy task. Passing tomahawk to 1.2 let us see more bug on myfaces 1.2,
and upgrade
tomahawk 1.1 apps should be easy. JSF 1.2 has more than one year and
JSF 2.0 is
coming. The only thing to be taken into account is continue doing
releases on
1.1 and that's all.
It's a matter of subjective opinions (all valid of course). But in my
humble opinion, better
move forward than stay quiet. Not one step back, nor to catch momentum.
regards
Leonardo Uribe
