Confirmed users
82
edits
DOM Inspector/Releases/Checklist: Difference between revisions
pull out the mention of release branches from the release day section
Sevenspade (talk | contribs) (→DOM Inspector release day: formatting) |
Sevenspade (talk | contribs) (pull out the mention of release branches from the release day section) |
||
| Line 1: | Line 1: | ||
This is a snapshot of the page, documenting a future process. Some things will not work with the current state of the DOM Inspector repository. | This is a snapshot of the page, documenting a future process. Some things will not work with the current state of the DOM Inspector repository. | ||
DOM Inspector releases are prepared from a release branch. Get there by doing updating to the branch point of the latest branch, then updating the working directory to the tip of the branch: | DOM Inspector releases are prepared from a release branch. Get there by doing updating to the branch point of the latest branch, then updating the working directory to the tip of the branch: | ||
<samp>$ <kbd>hg update DOMI_LATEST_BRANCH && hg update</kbd></samp> | <samp>$ <kbd>hg update DOMI_LATEST_BRANCH && hg update</kbd></samp> | ||
From | == DOM Inspector release day == | ||
From the release branch, the release process is as follows: | |||
* Verify that the maxVersion strings in install.rdf on the release branch for all applications match the versions that correspond to the current nightlies derived from mozilla-central. (This shouldn't be necessary if you've already done everything you're supposed to do on the last merge day.) | * Verify that the maxVersion strings in install.rdf on the release branch for all applications match the versions that correspond to the current nightlies derived from mozilla-central. (This shouldn't be necessary if you've already done everything you're supposed to do on the last merge day.) | ||
* Change the makefile to reflect the new version number. Use the tracking bug for that release in your commit. | * Change the makefile to reflect the new version number. Use the tracking bug for that release in your commit. | ||