DOM Inspector/Releases/Checklist - Revision history

Sevenspade: /* DOM Inspector branch days */ make a note about having to commit immediately after branching, and correct bug id

2012-07-11T22:29:30Z

DOM Inspector branch days: make a note about having to commit immediately after branching, and correct bug id

Sevenspade: bad bug dependency

2012-07-11T20:39:17Z

bad bug dependency

← Older revision		Revision as of 20:39, 11 July 2012
Line 74:		Line 74:
	* Switch back to the default branch<br/><nowiki>		* Switch back to the default branch<br/><nowiki>
	</nowiki><samp>$ <kbd>hg update default</kbd></samp>		</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~~.		* 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 new branch (which should already exist).
	** 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".		** 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". Make it depend on bug DOMi2.0.12.
	* Change the makefile on the default branch to reflect the new version number. Use the new tracking bug for your commit.		* 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].		** 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].

Sevenspade: /* DOM Inspector branch days */ add remove tag DOMI_LATEST_BRANCH step

2012-06-01T00:36:54Z

DOM Inspector branch days: add remove tag DOMI_LATEST_BRANCH step

← Older revision		Revision as of 00:36, 1 June 2012
Line 65:		Line 65:
	* 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.)
	* Verify that any translations updated on the last release branch have been copied over to the default branch.		* Verify that any translations updated on the last release branch have been copied over to the default branch.
			* Remove the DOMI_LATEST_BRANCH tag from the last branch<br/><nowiki>
			</nowiki><samp>$ <kbd>hg tag --remove DOMI_LATEST_BRANCH</kbd></samp>
	* 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>		** 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>

Sevenspade: /* DOM Inspector branch days */ Forgot about DOMI_LATEST_BRANCH tag

2012-05-31T23:41:06Z

DOM Inspector branch days: Forgot about DOMI_LATEST_BRANCH tag

← Older revision		Revision as of 23:41, 31 May 2012
Line 68:		Line 68:
	** 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>		** 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>		</nowiki><samp>$ <kbd>hg branch DOMI_2_0_12</kbd></samp>
			* Tag the new branch DOMI_LATEST_BRANCH<br/><nowiki>
			</nowiki><samp>$ <kbd>hg tag DOMI_LATEST_BRANCH</kbd></samp>
	* Switch back to the default branch<br/><nowiki>		* Switch back to the default branch<br/><nowiki>
	</nowiki><samp>$ <kbd>hg update default</kbd></samp>		</nowiki><samp>$ <kbd>hg update default</kbd></samp>

Sevenspade: /* DOM Inspector branch days */ new section

2012-05-31T23:32:43Z

DOM Inspector branch days: new section

← Older revision		Revision as of 23:32, 31 May 2012
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.

Sevenspade: pull out the mention of release branches from the release day section

2012-05-31T20:59:44Z

pull out the mention of release branches from the release day section

← Older revision		Revision as of 20:59, 31 May 2012
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 release day ==~~
	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 ~~there~~ the release process is as follows:		== 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.

Sevenspade: /* DOM Inspector release day */ formatting

2012-05-31T20:56:05Z

DOM Inspector release day: formatting

← Older revision		Revision as of 20:56, 31 May 2012
Line 11:		Line 11:
	** e.g., when releasing DOMi 2.0.12, you would change it from 2.0.12pre to 2.0.12 on the DOMI_2_0_12 branch. The commit message would be "Bug 738048 - (DOMi2.0.12) DOM Inspector 2.0.12". See [http://hg.mozilla.org/dom-inspector/rev/c42fd9baba56 changeset c42fd9baba56].		** e.g., when releasing DOMi 2.0.12, you would change it from 2.0.12pre to 2.0.12 on the DOMI_2_0_12 branch. The commit message would be "Bug 738048 - (DOMi2.0.12) DOM Inspector 2.0.12". See [http://hg.mozilla.org/dom-inspector/rev/c42fd9baba56 changeset c42fd9baba56].
	* Add a version-specific tag and a DOMI_LATEST_RELEASE tag		* Add a version-specific tag and a DOMI_LATEST_RELEASE tag
	** e.g., <br/><nowiki>		** e.g.,<br/><nowiki>
	</nowiki><samp>$ <kbd>hg tag DOMI_2_0_12_RELEASE</kbd></samp><br/><nowiki>		</nowiki><samp>$ <kbd>hg tag DOMI_2_0_12_RELEASE</kbd></samp><br/><nowiki>
	</nowiki><samp>$ <kbd>hg tag -r DOMI_2_0_12_RELEASE DOMI_LATEST_RELEASE</kbd></samp>		</nowiki><samp>$ <kbd>hg tag -r DOMI_2_0_12_RELEASE DOMI_LATEST_RELEASE</kbd></samp>
Line 19:		Line 19:
	*** This should work with other, non-Firefox mozilla-central project source drops since we're not actually going to build the application; we're just going to leverage the mozilla build system. It's just that the Firefox ftp directory includes a "latest" symlink, and others don't.		*** This should work with other, non-Firefox mozilla-central project source drops since we're not actually going to build the application; we're just going to leverage the mozilla build system. It's just that the Firefox ftp directory includes a "latest" symlink, and others don't.
	** Extract the source drop		** Extract the source drop
	*** e.g., <samp>:~/src$ <kbd>tar xjf ./firefox-12.0.source.tar.bz2<kbd></samp>		*** e.g.,<br/><nowiki>
			</nowiki><samp>:~/src$ <kbd>tar xjf ./firefox-12.0.source.tar.bz2<kbd></samp>
	** Drop dom-inspector into the extensions directory		** Drop dom-inspector into the extensions directory
	*** Clone the repo there		*** Clone the repo there:<br/><nowiki>
	~~****~~ <samp>:~/src/mozilla-release/$ <kbd>hg clone http://hg.mozilla.org/dom-inspector ./extensions/inspector</kbd></samp>		</nowiki><samp>:~/src/mozilla-release$ <kbd>hg clone http://hg.mozilla.org/dom-inspector ./extensions/inspector</kbd></samp>
	*** Update to the release branch		*** Update to the release branch:<br/><nowiki>
	~~****~~ <samp>:~/src/mozilla-release/$ <kbd>hg update -R ./extensions/inspector DOMI_LATEST_RELEASE</kbd></samp>		</nowiki><samp>:~/src/mozilla-release$ <kbd>hg update -R ./extensions/inspector DOMI_LATEST_RELEASE</kbd></samp>
	*** Alternatively, you can <kbd>mv</kbd>/<kbd>cp</kbd>/<kbd>hg archive</kbd> the repository you were working from before, but I usually clone a new one for good measure, since the dom-inspector repo is so small.		*** Alternatively, you can <kbd>mv</kbd>/<kbd>cp</kbd>/<kbd>hg archive</kbd> the repository you were working from before, but I usually clone a new one for good measure, since the dom-inspector repo is so small.
	** Edit the .mozconfig to enable DOM Inspector in the build (and nothing else)		** Edit the .mozconfig to enable DOM Inspector in the build (and nothing else):<br/><nowiki>
	~~***~~ <kbd>ac_add_options --enable-application=extensions<br/>ac_add_options --enable-extensions=inspector</kbd>		</nowiki><kbd>ac_add_options --enable-application=extensions<br/><nowiki>
	** Start the build		</nowiki>ac_add_options --enable-extensions=inspector</kbd>
	~~***~~ <samp>:~/src/mozilla-release/$ <kbd>make -f ./client.mk</kbd></samp>		** Start the build:<br/><nowiki>
			</nowiki><samp>:~/src/mozilla-release$ <kbd>make -f ./client.mk</kbd></samp>
	** Fish out the XPI from <var>$MOZOBJDIR</var>/dist/xpi-stage		** Fish out the XPI from <var>$MOZOBJDIR</var>/dist/xpi-stage
	*** e.g., ~/src/mozilla-release/objdir-i686-pc-linux-gnu/dist/xpi-stage/inspector-2.0.12.xpi		*** e.g., ~/src/mozilla-release/objdir-i686-pc-linux-gnu/dist/xpi-stage/inspector-2.0.12.xpi

Sevenspade: /* DOM Inspector release day */ order matters?

2012-05-31T20:48:51Z

DOM Inspector release day: order matters?

← Older revision		Revision as of 20:48, 31 May 2012
Line 4:		Line 4:
	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:

	<kbd>hg update DOMI_LATEST_BRANCH && hg update</kbd>		<samp>$ <kbd>hg update DOMI_LATEST_BRANCH && hg update</kbd></samp>

	From there the release process is as follows:		From there the release process is as follows:
Line 10:		Line 10:
	* 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.
	** e.g., when releasing DOMi 2.0.12, you would change it from 2.0.12pre to 2.0.12 on the DOMI_2_0_12 branch. The commit message would be "Bug 738048 - (DOMi2.0.12) DOM Inspector 2.0.12". See [http://hg.mozilla.org/dom-inspector/rev/c42fd9baba56 changeset c42fd9baba56].		** e.g., when releasing DOMi 2.0.12, you would change it from 2.0.12pre to 2.0.12 on the DOMI_2_0_12 branch. The commit message would be "Bug 738048 - (DOMi2.0.12) DOM Inspector 2.0.12". See [http://hg.mozilla.org/dom-inspector/rev/c42fd9baba56 changeset c42fd9baba56].
	* ~~Tag the release DOMI_LATEST_RELEASE and add~~ a version-specific tag		* Add a version-specific tag and a DOMI_LATEST_RELEASE tag
	** e.g., DOMI_2_0_12_RELEASE		** e.g., <br/><nowiki>
			</nowiki><samp>$ <kbd>hg tag DOMI_2_0_12_RELEASE</kbd></samp><br/><nowiki>
			</nowiki><samp>$ <kbd>hg tag -r DOMI_2_0_12_RELEASE DOMI_LATEST_RELEASE</kbd></samp>
	* Build it		* Build it
	** Download the latest mozilla-central release source drop		** Download the latest mozilla-central release source drop

Sevenspade: /* DOM Inspector release day */ remove colon; this is not a prompt

2012-05-31T20:10:17Z

DOM Inspector release day: remove colon; this is not a prompt

← Older revision		Revision as of 20:10, 31 May 2012
Line 29:		Line 29:
	*** <samp>:~/src/mozilla-release/$ <kbd>make -f ./client.mk</kbd></samp>		*** <samp>:~/src/mozilla-release/$ <kbd>make -f ./client.mk</kbd></samp>
	** Fish out the XPI from <var>$MOZOBJDIR</var>/dist/xpi-stage		** Fish out the XPI from <var>$MOZOBJDIR</var>/dist/xpi-stage
	*** e.g., :~/src/mozilla-release/objdir-i686-pc-linux-gnu/dist/xpi-stage/inspector-2.0.12.xpi		*** e.g., ~/src/mozilla-release/objdir-i686-pc-linux-gnu/dist/xpi-stage/inspector-2.0.12.xpi
	* Prepare the release notes		* Prepare the release notes
	** find the dependent bugs for release bug		** find the dependent bugs for release bug

Sevenspade: /* DOM Inspector release day */ finish the checklist (yay, interleaved escaping for idiosyncratic parsers)

2012-05-31T20:05:25Z

DOM Inspector release day: finish the checklist (yay, interleaved escaping for idiosyncratic parsers)

← Older revision		Revision as of 20:05, 31 May 2012
Line 30:		Line 30:
	** Fish out the XPI from <var>$MOZOBJDIR</var>/dist/xpi-stage		** Fish out the XPI from <var>$MOZOBJDIR</var>/dist/xpi-stage
	*** e.g., :~/src/mozilla-release/objdir-i686-pc-linux-gnu/dist/xpi-stage/inspector-2.0.12.xpi		*** e.g., :~/src/mozilla-release/objdir-i686-pc-linux-gnu/dist/xpi-stage/inspector-2.0.12.xpi
			* Prepare the release notes
			** find the dependent bugs for release bug
			*** e.g., bug DOMi2.0.12
			*** it's easy to copy and paste if you look at the dependency tree for the bug, at max depth 1, showing resolved
			**** e.g., https://bugzilla.mozilla.org/showdependencytree.cgi?id=738048&maxdepth=1&hide_resolved=0
			*** Ignore the tracking bug for the previous release; don't copy it into the release notes.
			** The notes take this form:<code><br/><nowiki>
			</nowiki><ul><br/><nowiki>
			</nowiki>  <li><br/><nowiki>
			</nowiki>    <a href="<var>URL</var>"<br/><nowiki>
			</nowiki>       title="Bug <var>bug id</var> - <var>bug summary</var>">Bug <var>bug id</var></a>&nbsp;- <var>bug summary</var> (patch by <var>contributor</var>)<br/><nowiki>
			</nowiki>  </li><br/><nowiki>
			</nowiki></ul><br/><nowiki>
			</nowiki><br/><nowiki>
			</nowiki>Localization fixes:<br/><nowiki>
			</nowiki><ul><br/><nowiki>
			</nowiki>  <li><var>Language</var>: <var>Contributor</var></li><br/><nowiki>
			</nowiki></ul><br/></code>
			** feel free to add explanatory text or additional prose above or below the notes
			* Submit it to AMO
			** Paste the release notes
			** Ping someone in [irc://irc.mozilla.org/addons #addons] for review
			* Leave a comment in the release bug about the AMO status
			* RESOLVE the bug when it gets reviewed and is made available on AMO

← Older revision		Revision as of 22:29, 11 July 2012
Line 67:		Line 67:
	* Remove the DOMI_LATEST_BRANCH tag from the last branch<br/><nowiki>		* Remove the DOMI_LATEST_BRANCH tag from the last branch<br/><nowiki>
	</nowiki><samp>$ <kbd>hg tag --remove DOMI_LATEST_BRANCH</kbd></samp>		</nowiki><samp>$ <kbd>hg tag --remove DOMI_LATEST_BRANCH</kbd></samp>
	* Branch		* Branch, and use the tracking bug that corresponds to the new branch for your commit.
	** 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>		** 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>		</nowiki><samp>$ <kbd>hg branch DOMI_2_0_12</kbd></samp>
			** The commit message would be "Bug 738048 - (DOMi2.0.12) DOM Inspector 2.0.12 (branch for localization)". Make sure you make your commit now, because tagging in the next step will steal the opportunity.
	* Tag the new branch DOMI_LATEST_BRANCH<br/><nowiki>		* Tag the new branch DOMI_LATEST_BRANCH<br/><nowiki>
	</nowiki><samp>$ <kbd>hg tag DOMI_LATEST_BRANCH</kbd></samp>		</nowiki><samp>$ <kbd>hg tag DOMI_LATEST_BRANCH</kbd></samp>
Line 79:		Line 80:
	** 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].		** 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.		* 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~~].		** 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=738048 bug 738048].
	* 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.		* 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.