[
https://issues.apache.org/jira/browse/TAPESTRY-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francois Armand updated TAPESTRY-2180:
--------------------------------------
Priority: Minor (was: Major)
Your comment seems fair, Tapestry 5 is still alpha and developers should be
aware that API and behavior may change (and eventually do).
Nonetheless, I think it would be good for early adopters to know that there is
somewhere a resource about the things that would break eventually after the
upgrade, and it might be hard to look every where in the doc to see if
something has changed. An example coming to mind is the Form validate event
name modification. Of course, it's a matter of minute to find the issue, but it
would be more pleasant to just have a check list of "thing to take care of
during upgrade".
Perhaps that the resource should be a wiki page on the topic, with at least the
main big change and links pointing to the updated documentation.
I will initialize that, and is the stuff grows to an useful resources, it might
be interesting to link the release note page to it.
What about that deal ?
> Add release notes about API changes
> -----------------------------------
>
> Key: TAPESTRY-2180
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2180
> Project: Tapestry
> Issue Type: Improvement
> Affects Versions: 5.0.3, 5.0.4, 5.0.5, 5.0.6, 5.0.7, 5.0.8, 5.0.9, 5.0.10
> Reporter: Francois Armand
> Priority: Minor
>
> Since the 5.0 final is in view (almost :), more and more users are upgrading
> from 5.0.5 / 5.0.6 / 5.0.7 version of Tapestry to newer ones.
> Yet, there was a lot of major behaviour modification since this time,
> especially in null / blanck parameters handling, Javascript and Ajax area,
> production mode, and certainly other.
> It would be great if the page
> http://tapestry.formos.com/nightly/tapestry5/tapestry-core/upgrade.html take
> inventory of these changes even before 5.0.11, perhaps with links to the
> matching JIRA issues.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
