Android Release Checklist

NEEDS TO BE REVIEWED...

  1. Build the tagged cordova-js for this version (cordova.android.js) from the cordova-js project, and put the file in the framework/assets/js folder, replacing the current cordova.android.js file

  2. Run all mobile-spec (JavaScript) unit-tests, and inspect the results, fix the bugs if necessary.

  3. Run all the manual tests (scroll down) and make sure the expectations are met as described in the manual test list in the link

  4. Run all native Android (Java) tests in the test directory, and inspect the results, fix the bugs if necessary.

  5. Update README.md (instructions, FAQ items) for the current version

  6. SHOULD ANDROID HAVE THIS (IT CURRENTLY DOESN'T)? Update releasenotes.md for the current version

    1. Grab changes from a previous tag to HEAD i.e if the previous tag was "Foo":
      •             git shortlog --no-merges Foo..HEAD
    2. Edit the commit logs - don't add the commits verbatim, usually they are meaningless to the user. Only show the ones relevant for the user (fixes, new features)
    3. Put the edited logs into a new section for the new version with a date (YYYYMMDD) in parentheses, and follow the previous formats
  7. Update the Cordova version data for the current version
    1. Update the VERSION file with the current version number

    2. Run bin/create, make sure it builds everything ok and that it actually generates an example project (ant build isn't good enough anymore)

    3. Create a commit that includes the following files
      1. VERSION

      2. bin/templates/project/assets/www/index.html

      3. framework/assets/js/cordova.android.js

      4. framework/assets/www/index.html

      5. framework/src/org/apache/cordova/Device.java

  8. If completion of the previous steps is satisfactory, tag your repo with the new version, then...
  9. Push your commits with the new tag to the Android repo

AndroidReleaseChecklist (last edited 2012-08-31 20:08:42 by SimonMacDonald)