SeaMonkey:Release Process:2.17b3

From MozillaWiki
Jump to: navigation, search

« SeaMonkey 2.17

Build Harness

SeaMonkey:Release Automation

Bugs

Tracking bug filed as bug 852840.

Build Engineer

  • ewong (mentor: Callek)

Signed-off Revisions

releases/comm-beta
 02c412fc57f1
releases/mozilla-beta
 FIREFOX_20_0b6_BUILD1
GECKO200b6_2013032008_RELBRANCH
dom-inspector
 863a04e7d1c5
DOMI_2_0_13
chatzilla
 79406f6ac9a2
SEA2_17_RELBRANCH
venkman
 b4bee5cb49dc
SEA2_17_RELBRANCH

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.17b3build1" doit
  • Tagging finished fine.
  • 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

  • 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

No longer needed to send info to metrics.


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 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 build to TrendMicro

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

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

Then do the cvs add command described in our website bug (if not already done)

Last: 

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.17b3-build1
~/bin/pushsnip Sea*2.17b3-build1

Send Announce

Send the announcement to newsgroups and about-mozilla.

Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey:Release_Process:2.17b3&oldid=640963"