On Mon, 28 Mar 2011 18:11:45 -0300, Howard Lewis Ship <[email protected]>
wrote:
In terms of another high level project under the Tapestry umbrella ...
I'd be for that if the "cost" of releasing new versions wasn't so
high. Having to make a change to plastic, then run through a
vote/release cycle, so that the change could be picked up (as a
non-snapshot version number) in tapestry-core seems unwieldy. Outside
Apache, you can Just Do It, but it would not be the Apache Way.
Keeping it under the Tapestry project means that it will have a
version number that tracks the other related projects that depend on
it, and they can transition from snapshot to release together.
What about Plastic as a member of the proposed Tapestry Extras?
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
