SeaMonkey:Release Process:2.0b2: Difference between revisions

← Older edit

SeaMonkey:Release Process:2.0b2 (view source)

Revision as of 23:22, 7 October 2009

470 bytes added , 7 October 2009

→‎Bugs

KaiRo

Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti

4,083

edits

@@ Line 3: / Line 3: @@
 == Bugs ==
-Tracking bug filed as {{bug|512085}}
+Tracking bug filed as {{bug|514294}}
 == Build Engineer ==
@@ Line 31: / Line 31: @@
 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 use those commands to do the following (now in <code>fakesign.sh</code>):
+Logged onto stage-old.mozilla.org and ran <code>fakesign.sh</code> as documented in [[SeaMonkey:Release_Process:2.0b1|2.0b1]] notes.
- # seabld@stage-old
- VERSION=2.0b2
- BUILD=1
- cd /home/ftp/pub/seamonkey/nightly/${VERSION}-candidates/build${BUILD}
- mkdir win32 update/win32
- rsync -av --exclude=*.zip unsigned/win32/ win32/
- rsync -av unsigned/update/win32/ update/win32/
- rsync -av unsigned/win32_info.txt .
- echo "faked" > win32_signing_build${BUILD}.log
-We purposely make copies here rather than symlinking for a couple of reasons: L10n verify scripts barf when they get zip files (hence the --exclude above), 'updates' factory will blow away complete MARs upon upload if update/win32 is a symlink. The echo creates the log the automation looks for, in order to continue to l10n verify and updates.
 === Updates and Verification ===
@@ Line 58: / Line 47: @@
 === Copy Language Packs ===
-Used <code>langpackmove.sh</code>as documented in [[SeaMonkey:Release_Process:2.0b1|2.0b1]] notes to move the langpacks into the directory we want them in for release.
+Used <code>langpackmove.sh</code> as documented in [[SeaMonkey:Release_Process:2.0b1|2.0b1]] notes to move the langpacks into the directory we want them in for release.
+=== Push To Mirrors ===
+With <code>make-checksums.sh</code> which I created last time around, I created MD5SUMS and SHA1SUMS files containing all files we release. Also, I copied the README from last time and modified it as needed.
+Then, with <code>mirrorpush.sh</code>, containing the line documented in [[SeaMonkey:Release_Process:2.0b1|2.0b1]] notes, I finally pushed 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 except cs, which fails (known) - still everything good to go!
+=== Publish Updates to the beta Channel ===
+ ~/bin/backupsnip 20090904-SeaMonkey-2.0b2
+ ~/bin/pushsnip 20090904-SeaMonkey-2.0b2
 == Wall Clock Time ==
@@ Line 121: / Line 125: @@
 ** End: Sat Sep 5 00:50:25 2009
 ** Elapsed: 1 hrs, 40 mins, 48 secs
+* final_verification (triggered manually after mirror push)
+** Start: Sat Sep 12 12:47:38 2009
+** End: Sat Sep 12 12:50:07 2009
+** Elapsed: 2 mins, 28 secs
+=== Final Push ===
+* Determined that QA coverage is OK in the European night of September 11
+* Did the actual push to mirrors at Sep 12 07:52 PDT 2009
+* pushsnip to beta channel at Sat Sep 12 15:44:03 PDT 2009