CloudServices/Sync/FxSync/PushingDevUpdates

From MozillaWiki
Jump to: navigation, search

Current instructions

Verify and tag changes

  1. update your repo to the tip of the appropriate branch
  2. run tests
    • make test
  3. update version in Makefile and commit that change
  4. tag that changeset with the version (i.e. 1.4.2)
    • hg tag -f <version> (use -f in case you're respinning)
  5. push changes
    • hg push

Get the locale set

  1. go to https://l10n-stage-sj.mozilla.org/shipping/dashboard?av=weave
  2. filter by sign-off == accepted
  3. grab that set of locales, and make them a comma-separated list
  4. for example: ar,be,ca,cs,de,es-AR,es-ES,fi,fr,fy-NL,hu,id,it,ja,ko,lt,nl,pa-IN,pt-BR,pt-PT,ru,sk,sq,tr,uk,vi,zh-CN,zh-TW

Build the XPI

  1. create an empty directory and cd to it
  2. run the following command:
    • python <path/to/repo>/tools/build_localized_addon.py -v <version> -locales <comma-separated list from above>
    • release builds add -release
  3. this should take a minute or so to complete, and you'll have a shiny new XPI in the directory

Updating Dev Channel builds

  1. upload builds to stage
    • scp weave-<a.b.N>-dev.xpi stage.mozilla.org:/home/ftp/pub/mozilla.org/labs/weave/development/<a.b.x>
  2. get QA to smoketest these builds
  3. while that is happening, you can update the web pieces
    1. update from svn+ssh://svn.mozilla.org/projects/services.mozilla.com/trunk/
    2. update sync/versions.php
      • Update $latest_dev to <version>
      • Update $latest_dev_date to <today>
      • Update $latest_dev_notes to include recent changes
    3. [SVN] commit changes to SVN
    4. [QA] verify changes on stage (might take ~5 minutes to kick in)
    5. Check http://services.stage.mozilla.com/sync/update.rdf for <version>
    6. Check http://services.stage.mozilla.com/sync/install.php for correct file
    7. Check http://services.stage.mozilla.com/sync/updated/?channel=dev&version=<ver> for version, date, notes
  4. Once QA signoff is complete, the current SVN should be tagged as production (requires access to tags/production)
    1. remove old production tag
    2. tag production as current trunk
  5. Wait for services.mozilla.com to auto-update, and verify a previous dev build updates

Old instructions

These will be archived at some point.

  1. [HG] update from ssh://hg.mozilla.org/labs/weave/
  2. [HG] bump Weave version to desired version in Makefile
  3. [make] run unit tests
    • make TOPSRCDIR=`pwd` test
  4. [HG] tag the version bump with the desired version
  5. create an empty directory
  6. [make] build the xpi
    • python <path/to/dev/repo>/tools/build_localized_addon.py -v <version>
  7. [HG] tag the version bump
    • hg tag <version>
  8. [HG] bump Weave version to the next version
  9. [HG] push version/tag changes
    • hg push
  10. [FTP] push build to ftp in the appropriate directory (labs/weave/development/a.b.x)
    • scp dist/xpi/weave-<ver>-dev.xpi stage.mozilla.org:...
  11. [SVN] update from svn+ssh://svn.mozilla.org/projects/services.mozilla.com/trunk/
  12. [SVN] update sync/versions.php
    1. Update $latest_dev to <version>
    2. Update $latest_dev_date to <today>
    3. Update $latest_dev_notes to include recent changes
  13. [SVN] commit changes to SVN
  14. [QA] verify changes on stage (might take ~5 minutes to kick in)
    1. Check http://services.stage.mozilla.com/sync/update.rdf for <version>
    2. Check http://services.stage.mozilla.com/sync/install.php for correct file
    3. Check http://services.stage.mozilla.com/sync/updated/?channel=dev&version=<ver> for version, date, notes
  15. [SVN] remove old production tag
  16. [SVN] if you have access (Mardak/mconnor do) tag production