SeaMonkey:Release Process:2.6.1 MU

From MozillaWiki
Jump to: navigation, search

MU

Update Patcher-Configs

  • For 2.0.14->2.6.1 MU we need to update Patcher Configs moz191-seamonkey-branch-major-patcher2.cfg
    • Replaced all refs of 2.4 to 2.6.1 in <current-update>...</current-update>
    • Replaced block of <2.4>...<2.4> in past updates with the block for 2.6.1 from mozRelease-seamonkey-branch-patcher2.cfg so that buildID's and URLs are all correct.
  • Checked in:
$ cvs ci -m "Bug 717117, update patcher-configs for 2.6.1 MU"
Checking in moz191-seamonkey-branch-major-patcher2.cfg;
/cvsroot/mozilla/tools/patcher-configs/moz191-seamonkey-branch-major-patcher2.cfg,v  <-- 
moz191-seamonkey-branch-major-patcher2.cfg
new revision: 1.15; previous revision: 1.14
done

Update Buildbot Configs

  • Updated build/buildbot-configs 99cbaabcd926 to point at the 1.9.1 based config as our primary, and to update the lines for 2.6.1 MU.
  • Updated and reconfigured buildmaster
    • Ran into error on reconfig, due to new master setup (1.9.1 config points at l10n-changesets and I never symlinked that, fixed with a symlink)

Run MU Builder

  • On web interface for major-update and hit the Force Build button.
    • FAILED somehow the system is showing two separate runs of this, but logs are only showing a single (later) run.
    • We investigated this failure too late to delve in closer for this issue.
  • Did a backout of the patcher-config and tools/ changes that our automation did, and re-ran force build.
    • This was all good (automation no longer checks a locale present in first build but not in new)

Push Updates to the release Channel

2.0.14 to 2.4

Note use SeaMonkey-2.0.14-build2-2.6.1-build1-MU

On aus |/opt/aus2/snippets/staging/|: 

~/bin/backupsnip SeaMonkey-2.0.14-build2-2.6.1-build1-MU
~/bin/pushsnip SeaMonkey-2.0.14-build2-2.6.1-build1-MU
Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey:Release_Process:2.6.1_MU&oldid=387471"