DOM Inspector/Releases/Checklist

From MozillaWiki
< DOM Inspector‎ | Releases
Revision as of 19:23, 31 May 2012 by Sevenspade (talk | contribs) (→‎DOM Inspector release day: restructure, change sample to use tag, lead into checklist, add a note about cloning a new copy to build from)
Jump to navigation Jump to search

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:

 hg update DOMI_LATEST_BRANCH && hg update

From there 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.)
  • 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 changeset c42fd9baba56.
  • Tag the release DOMI_LATEST_RELEASE and add a version-specific tag
    • e.g., DOMI_2_0_12_RELEASE
  • Build it
    • Download the latest mozilla-central release source drop
      • e.g., get it from ftp://ftp.mozilla.org/pub/firefox/releases/latest/source
      • 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
      • e.g., :~/src$ tar xjf ./firefox-12.0.source.tar.bz2
    • Drop dom-inspector into the extensions directory
      • :~/src/mozilla-release/$ hg clone http://hg.mozilla.org/dom-inspector ./extensions/inspector
      • Update to the release branch
        • :~/src/mozilla-release/$ hg update -R ./extensions/inspector DOMI_LATEST_RELEASE
      • Alternatively, you can mv/cp/hg archive 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 build DOM Inspector
      • ac_add_options --enable-application=extensions
        ac_add_options --enable-extensions=inspector
    • Start the build
      • :~/src/mozilla-release/$ make -f ./client.mk
    • Fish out the XPI from $MOZOBJDIR/dist/xpi-stage
      • e.g., :~/src/mozilla-release/objdir-i686-pc-linux-gnu/dist/xpi-stage/inspector-2.0.12.xpi