Personal tools

SeaMonkey:Release Process:2.7b3

From MozillaWiki

Jump to: navigation, search

Contents

« SeaMonkey 2.7

Build Harness

SeaMonkey:Release Automation

Bugs

Tracking bug filed as bug 715754

Build Engineer

  • Callek

Signed-off Revisions

releases/comm-beta
4fdc37506083
releases/mozilla-beta
FIREFOX_10_0b3_BUILD2
(GECKO100_2012010410_RELBRANCH)
dom-inspector
589ef9b749f5
(DOMI_2_0_10)
chatzilla
48d3ca3f72e4
venkman
a38583d7164a

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

Notes

  • Have to do the same s/mac/mac64/ work as in SeaMonkey 2.1b2. Will have to look into an easier way for that

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=Callek --master=localhost:9010 --branch=releases/comm-beta -c "SeaMonkey 2.7b2build1" doit
  • Tagging Good.
  • All Builds good.
  • All repacks good.

Update Version for stage scripts

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

Signing

  • Our mac builds (non en-US) uploaded to mac64/ so I had to move them over to mac/ on stage, for both updates and builds.
    • Logged onto stage-old.mozilla.org and ran sh ~/mac64tomac.sh
      • If existing you'll want to rm -rf mac64{,-u*} first. Otherwise mac64tomac will spit errors.
    • which moves all mac64 files/directories to mac, and removes the mac64 dir.
  • 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

Send info to metrics

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

SeaMonkey,seamonkey,seamonkey,2.7b3,2.7

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.
  • Update good.
  • Update verification 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.

  • Note to self: Panic not. There is no progress output for this step.

Push build to TrendMicro

I used the TrendMicro provided staging ftp directory to stage 2.5b3 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.

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.

Final Verification

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

  • Note to self: this part is expected to fail. Needs to be fixed.

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.7b2-build1.appVersion
~/bin/pushsnip Sea*2.7b2-build1.appVersion

WE ARE HERE

Send Announce

Send the announcement to newsgroups and about-mozilla.