Confirmed users
82
edits
DOM Inspector/Releases/Checklist: Difference between revisions
Jump to navigation
Jump to search
→DOM Inspector branch days: new section
Sevenspade (talk | contribs) (pull out the mention of release branches from the release day section) |
Sevenspade (talk | contribs) (→DOM Inspector branch days: new section) |
||
| Line 58: | Line 58: | ||
* Leave a comment in the release bug about the AMO status | * Leave a comment in the release bug about the AMO status | ||
* RESOLVE the bug when it gets reviewed and is made available on AMO | * RESOLVE the bug when it gets reviewed and is made available on AMO | ||
== DOM Inspector branch days == | |||
From the default branch, the branch 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 any translations updated on the last release branch have been copied over to the default branch. | |||
* Branch | |||
** e.g., if the last version of DOM Inspector released was 2.0.11, the current version on the default branch should already be 2.0.12pre, and the name for the new branch will be DOMI_2_0_12<br/><nowiki> | |||
</nowiki><samp>$ <kbd>hg branch DOMI_2_0_12</kbd></samp> | |||
* Switch back to the default branch<br/><nowiki> | |||
</nowiki><samp>$ <kbd>hg update default</kbd></samp> | |||
* Create a new tracking bug for the version of DOM Inspector that follows the version for the newly-created branch. Give it an alias and a summary that correspond to the version that it tracks, and make it depend on the tracking bug for the last version released. | |||
** e.g., if the name of the newly-created branch was DOMI_2_0_12, create a bug with the summary "DOM Inspector 2.0.13", and give it the alias "DOMi2.0.13". | |||
* Change the makefile on the default branch to reflect the new version number. Use the new tracking bug for your commit. | |||
** e.g., if you just branched DOMI_2_0_12 and created a tracking bug for DOM Inspector 2.0.13, you would change the makefile from 2.0.12pre to 2.0.13pre on the default branch. The commit message would be "Bug 748542 - (DOMi2.0.13) DOM Inspector 2.0.13 (bump version number to 2.0.13pre)". See [http://hg.mozilla.org/dom-inspector/rev/af3dd47abfe5 changeset af3dd47abfe5]. | |||
* Leave a comment in the tracking bug corresponding to the version that just branched. | |||
** e.g., if the newly-created branch is DOMI_2_0_12, you would leave a comment in [https://bugzilla.mozilla.org/show_bug.cgi?id=748542 bug 748542]. | |||
* Attempt to notify translators who are involved with out-of-date localizations that the repo has branched so that localizers have a stationary target for the next six weeks. | |||