Details

Description

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.

Howard M. Lewis Ship
added a comment - 20/Feb/08 17:09 Back dating these changes notes would be extremely difficult and, in my opinion, not a good use of the developer's time. Keeping the notes maintained going forward though should be a requirement.

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 ?

Francois Armand
added a comment - 21/Feb/08 10:40 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 ?