SeaMonkey:Release Process:2.11b5
Build Harness
Bugs
Tracking bug filed as bug 770871.
Build Engineer
- ewong (mentor: Callek)
Signed-off Revisions
- releases/comm-beta
- abd2f550bdd7
- releases/mozilla-beta
- FIREFOX_14_0b11_BUILD1
GECKO140_2012070408_RELBRANCH
- dom-inspector
- 6b5ec09f3b1d
DOMI_2_0_12
- 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.11b5build1" doit
- Tagging finished fine, but was bogus as it did not do what it was supposed to do.
- It did not create the proper tags and thusly source/builds/repacks all failed.
- Problem was the previous beta release, the skip-tag was set to True. Need it to be set to false.
- Reset the skip-tag to false. Pushed changes to buildbot-configs.
- Redid sendchange.
- Tag failed again. This time. "hg push fi failed".
- failed because of some ""remote: Could not chdir to home directory : No such file or directory" error.
- Tag failed again. This time. "hg push fi failed".
- Clobbered and redid the sendchange.
- Sendchange cancelled. Callek did some magic.
- Tagging finished fine.
- All Builds good.
- All repacks good!
- Callek manually retriggered win32_build. I retriggered the win32_l10n_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.11b5,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.11b5 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.11b5-build1 ~/bin/pushsnip Sea*2.11b5-build1
Send Announce
Send the announcement to newsgroups and about-mozilla.
