SeaMonkey:Release Process:2.0a3

Build Engineer

Robert Kaiser

Signed-off Revisions

http://hg.mozilla.org/comm-central/rev/4b85ed8f77b9
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/a4093e9930cf
http://hg.mozilla.org/dom-inspector/rev/5a93979aeccc
cvs trunk as of 2009-02-18 12:00 PST

Build 2

http://hg.mozilla.org/comm-central/rev/de44b92d06d2 (all others: same as build 1)

Bugs

Tracking bug filed as bug 479118

Tags

Tagging

Done on my local machine with the script attached on the bug, started to run at slightly post 2009-02-18 15:00 PST and ran until 15:45 PST (mozilla-1.9.1 took quite long due to my connection being clogged). Unfortunately, that script changed too much in client.py and I only spotted that after doing the last push manually. I also needed to rebase that tagging on 1.9.1 and DOMi to be able to push without creating new heads. With those fixups, the tagging was finished at 16:07 PST.

Used the following command to run and generate the log:

(projects/tag-seamonkey.sh 2>&1) | tee -a ./tag-seamonkey-2.0a3.log

Build 2

Started at about 2009-02-23 12:45 PST and was finished at about 13:15 PST, I updated the script but actually pushing the tags didn't want to work right away so I needed to do that manually once again. The new version of the script creates the log by itself though.

Build 1

Started to work on the machines about 2009-02-18 16:10 PST, running the script attached to the bug on all machines, from a screen session via ssh on Linux, a terminal window on Mac and a mozilla-build bash window on Windows. At 2009-02-18 17:00 PST, all the builds were running and I could leave the machines alone for the time being. I needed to restart the Windows builds with turned-off buildbot slave on that machine on the next day, as compiling the jemalloc CRT had run into strange trouble. Worked fine the second time with the same script though.

Source tarball was created and staged automatically, all builds were staged automatically by the build script.

Build data

Build 2

Started to work on the machines about 2009-02-23 13:30 PST, running the same script as for build 1 but with the BUILD var changed to 2. At 2009-02-18 13:45 PST, all the builds were running and I could leave the machines alone for the time being.

Build data