SeaMonkey:Release Process:2.3.3

From MozillaWiki
Jump to: navigation, search

« SeaMonkey 2.3.3

Build Harness

SeaMonkey:Release Automation

Bugs

Tracking bug filed as bug 683719

Build Engineer

Justin Wood

Signed-off Revisions

releases/comm-release
 311f330a36a6
releases/mozilla-release
 7a4871571868
(SEAMONKEY_2_3_3_RELBRANCH)
dom-inspector
 DOMI_2_0_10_RELEASE
(DOMI_2_0_10)
chatzilla
 144f0c279a3b
venkman
 5e7659a617fa

L10n revisions to be based on what was shipped in SeaMonkey 2.3. No updates for l10n.

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
  • Enabled the version bumping for this release, as we'll be 2.3.3
  • Re-Relbranched on m-release, to save confusion.

Build

  • Made sure all build machines have clean release directories.
    • Manually on windows, jumphost sh relclean.sh
  • Updated build/buildbot-configs for configs
  • Updated and reconfigured buildmaster
  • Kicked off with the following command:
buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-release -c "SeaMonkey 2.3.3build1" doit
  • Tagging completed fine
  • Linux64 failed with the config clone, retriggered, and that finished fine.
  • All repacks finished fine.

Fake tr locale

Not Needed for this build

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
    • 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

Updates and Verification

  • _l10n_verify and updates started automatically, triggered by the fake-signing.
    • All good, no string changes.

Updates on release channel to 2.3.3

  • Update finished ok
  • Verifications finished ok

Updates from beta's to 2.3.3

  • Following the lead of Firefox6.0 we're manually creating Updates from 2.3beta's as well.

Used cb-seamonkey-linux-02 which generated the updates 

cd /builds/slave/rel*updates/build
# Bump mozBeta-seamonkey-branch-patcher2.cfg, no -u needed
PERL5LIB=../tools/lib/perl perl ../tools/release/patcher-config-bump.pl \
 -p seamonkey -r SeaMonkey -v 2.3.3 -a 2.3.3 -o 2.3.2 -b 1 \
 -c patcher-configs/mozBeta-seamonkey-branch-patcher2.cfg \
 -t stage-old.mozilla.org -f ftp.mozilla.org \
 -d download.mozilla.org -l shipped-locales --platform linux \
 --platform macosx64 --platform win32 --marname seamonkey \
 --oldmarname seamonkey

# Sanity check  
cvs -q diff -u patcher-configs/mozBeta-seamonkey-branch-patcher2.cfg

cvs -q commit \
  -m "Configuration bump: mozBeta-seamonkey-branch-patcher2.cfg, from 2.3.2 to 2.3.3 build 1" \
  patcher-configs/mozBeta-seamonkey-branch-patcher2.cfg

# Patch Info Only since 2.3.2->2.3.3 release
#   automation created partials already.
# Since previous run was never removed, this auto-combines for beta.
perl patcher2.pl --create-patchinfo --partial-patchlist-file=patchlist.cfg \
  --app=seamonkey --brand=SeaMonkey \
  --config=patcher-configs/mozBeta-seamonkey-branch-patcher2.cfg

find temp/seamonkey/2.3.2-2.3.3/ftp/seamonkey/nightly/2.3.3-candidates/build1 \
   -type f -exec chmod 644 '{}' ';'
find temp/seamonkey/2.3.2-2.3.3/ftp/seamonkey/nightly/2.3.3-candidates/build1 \
   -type d -exec chmod 755 '{}' ';'

rsync -av -e 'ssh -oIdentityFile=~/.ssh/seabld_dsa' \
   temp/seamonkey/2.3.2-2.3.3/aus2.test/ \
   seabld@aus2-community.mozilla.org:/opt/aus2/snippets/staging/SeaMonkey-2.3.3-build1-combined-test
rsync -av -e 'ssh -oIdentityFile=~/.ssh/seabld_dsa' \
   temp/seamonkey/2.3.2-2.3.3/aus2.beta/ \
   seabld@aus2-community.mozilla.org:/opt/aus2/snippets/staging/SeaMonkey-2.3.3-build1-combined-beta

Push to the betatest channel 

# seabld@aus2-community.mozilla.org
cd /opt/aus2/snippets/staging/
~/bin/backupsnip SeaMonkey-2.3.3-build1-combined-test
~/bin/pushsnip SeaMonkey-2.3.3-build1-combined-test

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 Updates to the beta Channel

Note use: SeaMonkey-2.3.3-build1-combined-beta

On aus |/opt/aus2/snippets/staging/|: 

~/bin/backupsnip SeaMonkey-2.3.3-build1-combined-beta
~/bin/pushsnip SeaMonkey-2.3.3-build1-combined-beta

Final Verification

Used 'Force Build' to start the final_verification builder; TODO

all tested URLs are HTTP 200 and 302 - ready for going public!

(One failed, but manual test of that mirror url was fine)

Push Updates to the release Channel

Note use SeaMonkey-2.3.3-build1

On aus |/opt/aus2/snippets/staging/|: 

~/bin/backupsnip SeaMonkey-2.3.3-build1
~/bin/pushsnip SeaMonkey-2.3.3-build1

WE ARE HERE

Push build to TrendMicro

I used the TrendMicro provided staging ftp directory to stage 2.1rc1 en-us win32 for them to scan, and be sure there are no false-positives.

Announce

  • Send announcement to mailing lists/newsgroups
  • Post announcement on SeaMonkey Blog
Retrieved from "https://wiki.mozilla.org/index.php?title=SeaMonkey:Release_Process:2.3.3&oldid=347199"