Tracking bug filed as bug 1055928.
- ewong (mentor: Callek)
L10n revisions according to opt-ins as taken from the sign-off tool (and pushed ship-it).
WE ARE HERE
[NB: This whole build had been fraught with bustages due to the fact we changed the steps to use mock. This required a LOT of changes to buildbot-config/buildbotcustom code. bug 840427 to be specific. backing out was 'fun'.
cvs backout: (for cvs.mozilla.org:/cvsroot/mozilla/tools/patcher)
- cvs update
- cvs log <filename>
- cvs update -j <bad version> -j <good version> <filename>
- cvs ci -m "<commit message>"
hg backout (for hg.mozilla.org/user/Callek_gmail.com/tools)
- hg update
- hg backout -r <revision to backout>
- hg commit -m <message>
- hg push ssh://hg.mozilla.org/user/Callek_gmail.com/tools -e 'ssh -l <email>'
- 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.25b2build1" doit
Update Version for stage scripts
On stage-old.mozilla.org, modified ~/versions.sh for the current release run.
- 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
- 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 & Update Verification were dismally busted due to a plethora of reasons.
- Over IRC, Callek gave the go-ahead to just proceed with the release but no updates.
Copy Language Packs
langpackmove.sh as documented in 2.0b1 notes to move the langpacks into the directory we want them in for release.
zipcopy.sh as documented in 2.0b1 notes to move the Windows zips into the directory we want them in for release.
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
mirrorpush.sh as documented in 2.0.3 notes to finally push the files to the public dir for mirrors to pick them up.
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
cvs up -Pd
Then do the
cvs add command described in our website bug (if not already done)
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.26b2-build1 ~/bin/pushsnip Sea*2.26b2-build1
Send the announcement to newsgroups and about-mozilla.