Jetpack/Release Process

Release Steps

1. Create separate, version-labeled tickets for each of the release touch-points
2. Once each of the tickets in the tracking bug is completed, create an update request to Atul Varma to push the release live.

Release Touchpoints

• Mozilla Labs Jetpack Sub-domain
  • Responsible: Aza Raskin

• Mozilla Labs Main Blog
  • Responsible: Aza Raskin or Daniel Buchner

• Jetpack Google Group
  • Responsible: Daniel Buchner

• FlightDeck SDK Content
  • Responsible: Daniel Buchner

• MDC Documentation
  • Responsible: TBD Documentation Czar

• Jetpack Ambassador Materials and Talking-points
  • Responsible: Aza Raskin

Build/Package/Push the SDK

Note: The examples in these instructions demonstrate the process with the 0.1rc2 release. When following this process, replace references to that release with the appropriate references to the release you are handling.

To build and package the SDK, clone and enter the repository:

hg clone ssh://hg.mozilla.org/labs/jetpack-sdk/ jetpack-sdk
cd jetpack-sdk

Update the reference to the release version in static-files/index.html to the version you are releasing (f.e. 0.1rc2), then commit the change:

hg commit -m"update version for next release"

Note: The Jetpack SDK uses numerically consecutive versions to denote major releases (0.1, 0.2, etc.). Development cycles use the version of the next release followed by "pre" (0.1pre before 0.1, 0.2pre before 0.2, etc.). Release candidates use the version of the release followed by "rc" and the number of the candidate (0.1rc1, 0.1rc2, etc.). And stabilization cycles between RCs use the version of the next RC followed by "pre" (0.1rc1pre before 0.1rc1, 0.1rc2pre before 0.1rc2, etc.)

Tag the repository with the version:

hg tag 0.1rc2

Update the reference to the release version in static-files/index.html to the version of the next cycle (f.e. 0.1rc3pre), then commit the change:

hg commit -m"update version for next cycle"

Push the changes to the central repository:

hg push

The central repository will automatically build tarball and ZIP archive packages based on the tag you committed and pushed. Download the packages from their tag-based location in the archive subdirectory of the central repository:

https://hg.mozilla.org/labs/jetpack-sdk/archive/0.1rc2.tar.gz
https://hg.mozilla.org/labs/jetpack-sdk/archive/0.1rc2.zip

Push the packages to the staging server:

scp 0.1rc2.tar.gz 0.1rc2.zip stage.mozilla.org:/pub/mozilla.org/labs/jetpack/

The packages should now be available on the distribution server:

https://ftp.mozilla.org/pub/mozilla.org/labs/jetpack/0.1rc2.tar.gz
https://ftp.mozilla.org/pub/mozilla.org/labs/jetpack/0.1rc2.zip