Jetpack/Release Process: Difference between revisions

Jump to navigation Jump to search

Jetpack/Release Process (view source)

Revision as of 23:38, 6 December 2011

14 bytes added ,  6 December 2011
update process to reflect new 'git-describe'-based no-.version version handling
m (clarification: the release tag is necessarily a child of the final RC, not the RC itself, as it also merges in the previous release)
(update process to reflect new 'git-describe'-based no-.version version handling)
Line 130: Line 130:
  git checkout master
  git checkout master


Set JPCV (Jetpack Current Version) to the current version identifier on the master branch (f.e. 1.2a0):
Set JPCV (Jetpack Current Version) to the version for which you are starting the release process: what the stabilization branch will turn into. If 'cfx --version' on master at this point reports "1.2-dev-SOMETHING", then JPCV will be "1.2":


  export JPCV=`cat .version`
  export JPCV=(UPCOMING VERSION)


Set JPNV (Jetpack Next Version) to the next version identifier on the master branch (f.e. 1.3a0):
Set JPNV (Jetpack Next Version) to the next-higher version identifier: what master will turn into the next time it is merged to stabilization, e.g. 1.3:


  export JPNV=(NEXT VERSION)
  export JPNV=(NEXT VERSION)


Change the version identifier on the master branch for the next development cycle:
Change the Firefox minVersion/maxVersion compatibility identifiers on the master branch to the values on the Firefox aurora/central branches.


find .version * -type f -exec perl -pi -e "s/${JPCV}/${JPNV}/g" {} \;
Commit the changes:


Verify that the version identifiers were changed correctly. In particular, make sure the find/replace command didn't modify strings that aren't SDK version identifiers but look similar to them (f.e. a version identifier in the jQuery library).
git commit -a -m"update Firefox minVersion/maxVersion to aurora/central versions of Firefox"
 
Commit the changes:


git commit -a -m"update SDK version to ${JPNV} for next development cycle"
Record an empty commit, to mark where master development switches from one release to the next:


Change the Firefox minVersion/maxVersion compatibility identifiers on the master branch to the values on the Firefox aurora/central branches.
git commit --allow-empty -m "branched off (JPCV), master is now destined to become (JPNV)"


Commit the changes:
Add a development tag to master, so subsequent checkouts self-identify as headed towards the next release:


  git commit -a -m"update Firefox minVersion/maxVersion to aurora/central versions of Firefox"
  git tag JPNV-dev


Check out the stabilization branch:
Check out the stabilization branch:
Warner
Confirmed users
471

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/376310"

Navigation menu