SeaMonkey:Release Process:2.11b4

From MozillaWiki
Jump to: navigation, search

« SeaMonkey 2.11

Build Harness

SeaMonkey:Release Automation

Bugs

Tracking bug filed as bug 769143.

Build Engineer

  • ewong (mentor: Callek)

Signed-off Revisions

releases/comm-beta
 f4b5b44d2f8b
releases/mozilla-beta
 FIREFOX_14_0b10_BUILD1
GECKO140_2012062805_RELBRANCH
dom-inspector
 DOMI_2_0_12_RELEASE
chatzilla
 CHATZILLA_0_9_88_2_RELEASE
venkman
 VENKMAN_RELEASE_0_9_89

L10n revisions according to opt-ins as taken from the sign-off tool (and pushed ship-it).

Notes

Build

  • Made sure all build machines have clean release directories.
    • With clobberer
  • Updated buildbot-configs for l10n and configs
  • Updated and reconfigured buildmaster
  • Kicked off with the following command:
bin/buildbot sendchange --username=ewong --master=localhost:9010 --branch=releases/comm-beta -c "SeaMonkey 2.11b4build1" doit
  • For some unknown reasons, tagging failed at failed hg_push_3.
    • Logged on to cn-sea-qm-centos5-01 and executed the exact same command:
  • source step failed :upload files failed.
    • Logged on to sea-vm-linux32-1 and ran the command:
      • "python comm-beta/mozilla/build/upload.py --base-path . source/seamonkey-2.11b4.source.tar.bz2"
      • worked, so clicked on the source Force Rebuild.
  • all the builds choked on make_uploads due to some upstream changes.
    • Callek applied some releng magic.
  • some builds worked. macosx64 build failed. linux_repack failed. possibly related to a patch pushed to stage proper.
    • Needed to manually trigger repacks.

Update Version for stage scripts

On stage-old.mozilla.org, modified ~/versions.sh for the current release run.


Signing

  • We have no signing infrastructure for SeaMonkey right now, so I faked the signing step that is usually done after completion of builds and L10n repacks and before the update generation.
  • Logged onto stage-old.mozilla.org and ran sh ~/fakesign.sh
  • signing good

Send info to metrics

Sent the following to metrics (metrics-alerts at mozilla dot org) as the only body of the e-mail, CC'ing seamonkey-release list. 

SeaMonkey,seamonkey,seamonkey,2.11b4,2.11

Updates and Verification

  • _l10n_verify and updates started automatically, triggered by the fake-signing.
    • L10n verification is mostly useless, since we have lots of expected changed strings.
  • Then Update was good.
  • Update Verification was good.

Copy Language Packs

Used langpackmove.sh as documented in 2.0b1 notes to move the langpacks into the directory we want them in for release.

Zipcopy

Used zipcopy.sh as documented in 2.0b1 notes to move the Windows zips into the directory we want them in for release.

Create Checksums

With make-checksums.sh as documented in 2.0.3 notes, created MD5SUMS and SHA1SUMS files containing all files we release - copying the README from last time and replacing the versions as needed, as well as doing the same for Linux x86_64.

Push To Mirrors

Used mirrorpush.sh as documented in 2.0.3 notes to finally push the files to the public dir for mirrors to pick them up.

Push build to TrendMicro

I used the TrendMicro provided staging ftp directory to stage 2.10b2 win32 (all locales) for them to scan, and be sure there are no false-positives.

  • Used |viruspush.sh| on stage for this.

E-mailed our TrendMicro contact to let him know of the new version available on their FTP server.

WE ARE HERE

Final Verification

Used 'Force Build' to start the final_verification builder; all tested URLs are HTTP 200 and 302 - ready for going public!

Push website updates Live

locally: 

cvs up -Pd && patch -p0 < patch && cvs ci -m ....

Push Updates to the beta Channel

Once website updates are live

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

~/bin/backupsnip Sea*2.11b3-build1
~/bin/pushsnip Sea*2.11b3-build1

Send Announce

Send the announcement to newsgroups and about-mozilla.

Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey:Release_Process:2.11b4&oldid=446900"