[jira] Resolved: (PIVOT-643) Create one or more upgrade guides to help users transition between Pivot releases

["Greg Brown (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PIVOT-643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Greg Brown resolved PIVOT-643.
------------------------------

    Resolution: Fixed

A document describing the major changes between 1.5.x and 2.0 has been added to the wiki:

https://cwiki.apache.org/confluence/display/PIVOT/Major+Feature+Changes+Between+1.5.x+and+2.0


> Create one or more upgrade guides to help users transition between Pivot releases
> ---------------------------------------------------------------------------------
>
>                 Key: PIVOT-643
>                 URL: https://issues.apache.org/jira/browse/PIVOT-643
>             Project: Pivot
>          Issue Type: Task
>         Environment: n/a
>            Reporter: Chris Bartlett
>            Assignee: Greg Brown
>             Fix For: 2.0
>
>
> I view a 1.5.1 to 2.0 guide as a necessity, but we could also have a 1.5 to 1.5.1 one.
> The guides might take the form of a publicly editable section on the wiki, or a more static guide on http://pivot.apache.org (hopefully updated if more issues come to light)
> One way of addressing this would be to take the example, demo & tutorial source from the prior release (1.5.x) and attempt to build it against the new release (2.0).  This would hopefully uncover most of the issues that users might face due to changes between the versions.
> Where possible, each 'issue' would be documented with a description of how it manifests (compilation error, runtime exception, silent), how to fix and other related issues.
> We can also suggest an ordered series of steps to be followed in order to try to reduce the potential volume of requests on the user mailing list.  (Run the wtkx -> bxml sconversion script, address issue x before issue y, then a, b & c ...)
> For skin styles, creation of a simple table of what has been renamed, removed & added in this release might suffice, with a note if the functionality has changed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.