Jetpack/Release Process: Difference between revisions

Jump to navigation Jump to search
Make the version identifier get syntax correct (eg $JPCV) for copy-paste friendliness
(improve merge-commit message)
(Make the version identifier get syntax correct (eg $JPCV) for copy-paste friendliness)
Line 151: Line 151:
Record an empty commit, to mark where master development switches from one release to the next:
Record an empty commit, to mark where master development switches from one release to the next:


  git commit --allow-empty -m "branched off (JPCV), master is now destined to become (JPNV)"
  git commit --allow-empty -m "branched off $JPCV, master is now destined to become $JPNV"


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


  git tag JPNV-dev
  git tag $JPNV-dev


Change the Firefox minVersion/maxVersion compatibility identifiers on the master branch to the values on the Firefox aurora/central branches.
Change the Firefox minVersion/maxVersion compatibility identifiers on the master branch to the values on the Firefox aurora/central branches.
Confirmed users
396

edits

Navigation menu