+1. And we'd have an automatic documentation about what was removed just by generating the release
notes from JIRA.
Uli
On 07.02.2011 12:17, Igor Drobiazko wrote:
Wouldn't it be better to create several JIRA issues for the removal of
deprecated stuff? This way we could point the users to the issues in case of
questions or upgrade problems.
On Sun, Feb 6, 2011 at 10:29 PM, Howard Lewis Ship<[email protected]> wrote:
I'm doing a lot of work in trunk (5.3.0) to start removing classes
that were @Deprecated in 5.2 and earlier. So far, it's been some
minor things not visible to most users, plus @ApplicationState,
@IncludeJavaScriptLibrary and @IncludeStylesheet.
There's quite a few more I want to hit, including PrimaryKeyEncoder,
RenderSupport, and the old page pooling mechanism.as well as the
URLRewriter stuff that was replaced with the LinkTransformer.
If you know something that's @Deprecated in 5.2 and think there's a
compelling reason to extend support for it for another release, please
speak up!
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
