incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Maj (JIRA)" <>
Subject [jira] [Updated] (CB-676) Improve PhoneGap migration guidance
Date Thu, 10 May 2012 18:24:51 GMT


Filip Maj updated CB-676:

          Component/s:     (was: iOS)
    Affects Version/s: 1.0.0

Shaz has already been doing a great job writing migration guides for each version for iOS.

Let's keep this issue as the top-level issue for migration guides as a whole in cordova. The
docs should house guides for upgrading projects between specific versions.

We should create sub-tasks in this issue for each platform, for each missing version of the
guide (ideally we will write guides for previous versions as well). We still have tons of
users on 1.2, 1.3, 1.4.1, etc., and they are not upgrading due to, among other things, lack
of guidance in this area.

Need to stub out markdown files in the docs for these upgrade guides.
> Improve PhoneGap migration guidance
> -----------------------------------
>                 Key: CB-676
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Docs
>    Affects Versions: 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.6.1, 1.7.0, 1.8.0
>            Reporter: Andrew Trice
> Guidance of migrating an old PhoneGap project to a new version is not easy to find. It
would be nice to have resources identifying how to upgrade a project that are easily accessible
on the web (docs or phonegap download page) - this could be simple instructions which libraries
to swap out, and what JS files have changed.   Since there isn't much content out and easy
to find now, this probably would go a long way to help PhoneGap users who want to upgrade
to a newer SDK.
> (Feedback based on communication with Adobe customers)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message