SeaMonkey:Release Process:2.15b1
Build Harness
Bugs
Tracking bug filed as bug 813820.
Build Engineer
- TBD
Signed-off Revisions
- releases/comm-beta
- b37400660da0
- releases/mozilla-beta
- FIREFOX_18_0b1_BUILD1
GECKO180_2012112110_RELBRANCH
- dom-inspector
- 94ddc709132f
DOMI_2_0_13
- chatzilla
- fd1768d10fd3
SEA2_15_RELBRANCH
- venkman
- 9a50ff3efb84
SEA2_15_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.15b1build1" doit
- Tagging, building and repacks needed to be redone:
*due to* : - issue with mozconfigs not being portedto comm-beta - wrong tags pushed in original patch.
- Callek fixed and repsun the whole process again.
- Tagging finished fine.
- All Builds good.
- All repacks good.
- linux-pl repack had to be manually redone as it failed.
Update Version for stage scripts
On stage-old.mozilla.org, modified ~/versions.sh for the current release run.
WE ARE HERE
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
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.13b6 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!
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.15b1-build1 ~/bin/pushsnip Sea*2.15b1-build1
Send Announce
Send the announcement to newsgroups and about-mozilla.