SeaMonkey:Release Process:2.1b3: Difference between revisions

← Older edit

SeaMonkey:Release Process:2.1b3 (view source)

Revision as of 20:38, 9 April 2011

8,076 bytes added , 9 April 2011

→‎Push To Mirrors

Callek

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

1,529

edits

@@ Line 12: / Line 12: @@
 == Signed-off Revisions ==
 ;comm-central
-:[http://hg.mozilla.org/comm-central/rev/4af4a784e99c 4af4a784e99c]
+:[http://hg.mozilla.org/comm-central/rev/4af4a784e99c 4af4a784e99c] (Built with)
+:[http://hg.mozilla.org/comm-central/rev/efa612d2641a efa612d2641a] (Updated shipped-locales and moved tags)
 ;releases/mozilla-2.0
 :[http://hg.mozilla.org/releases/mozilla-2.0/rev/b5a576b9a3e0 b5a576b9a3e0]
@@ Line 33: / Line 34: @@
 * Kicked off with the following command:
   buildbot sendchange --username=Callek --master=localhost:9010 --branch=releases/comm-1.9.1 -c "SeaMonkey 2.1b3build1" doit
+* Did the wrong --branch here, but caught that and fixed. But before I re-sent I noticed that I didn't update the buildbot branch for comm-2.0 anyway ([http://hg.mozilla.org/build/buildbot-configs/rev/aa40f4da118a xref])
+** Updated and Reconfigured for that.
+* Kicked off with the following command:
+ buildbot sendchange --username=Callek --master=localhost:9010 --branch=comm-central -c "SeaMonkey 2.1b3build1" doit
+* Had a bad cZ changeset entered (copy/paste error), fixed in [http://hg.mozilla.org/build/buildbot-configs/rev/a0856363f207 new push]
+** Updated and Reconfigured for that.
+* Kicked off ''again'' with the following command:
+ buildbot sendchange --username=Callek --master=localhost:9010 --branch=comm-central -c "SeaMonkey 2.1b3build1" doit
+* We failed three of our signed off locales, '''nb-NO''', '''fi''', '''sv-SE'''. Holding next steps until I get an ok to ship without them (from our l10n coordinator)
+** Got an OK from KaiRo for moving forward with this, had to update shipped-locales due to the failure here (See new cset above), I moved the tags so that we don't need a build2.
+=== Fake tr locale ===
+In order for bouncer/sentry to see our files, I created fake tr locale files on ftp:
+ mkdir "win32/tr" "linux-i686/tr" "mac/tr"
+ mkdir "update/win32/tr" "update/linux-i686/tr" "update/mac/tr"
+ touch "win32/tr/SeaMonkey Setup 2.1 Beta 3.exe" \
+ "linux-i686/tr/seamonkey-2.1b3.tar.bz2" \
+ "mac/tr/SeaMonkey%202.1%20Beta%203.dmg" \
+ "win32/tr/seamonkey-2.1b3.complete.mar" \
+ "update/linux-i686/tr/seamonkey-2.1b3.complete.mar" \
+ "update/mac/tr/seamonkey-2.1b3.complete.mar"
+ mv win32/tr/*.mar update/win32/tr
+=== 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.
+** From build1 dir: <code>rsync -av mac64/ mac/</code> and <code>rm -rf mac64</code>
+** From updates dir: <code>rsync -av mac64/ mac/</code> and <code>rm -rf mac64</code>
+* 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 <code>sh ~/fakesign.sh</code>
+=== Updates and Verification ===
-== Wall Clock Time ==
+*_l10n_verify and updates started automatically, triggered by the fake-signing.
+** L10n verification is mostly useless, since we have many new locales, and lots of expected changed strings.
+* update completed fine
+** the Update verification was red for all platforms, due to the dropping of 4 locales that were in b2: ''`it`'', ''`fi`'', ''`nb-NO`'', ''`sv-SE`''. This is ok in this case. Everything else was fine.
-=== Build ===
+=== Copy Language Packs ===
-* buildbot sendchange: Tue Apr  5 22:12:55 PDT 2011
-* tag:
+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.
-* source:
-* linux_build:
+=== Zipcopy ===
-* linux64_build:
+Used <code>zipcopy.sh</code> as documented in [[SeaMonkey:Release_Process:2.0b1|2.0b1]] notes to move the Windows zips into the directory we want them in for release.
-* win32_build:
-* macosx_build:
+=== Create Checksums ===
-* linux_repack (23 locales):
-* win32_repack (23 locales):
+With <code>make-checksums.sh</code> as documented in [[SeaMonkey:Release_Process:2.0.3|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.
-* macosx_repack (23 locales):
-* updates:
+=== Update the README on FTP ===
+The README file we copy over from 2.1b2 needed a manual Update as the PRETTYNAME with version doesn't get updated by the scripts we use. I also noticed that we still referenced PPC in that, so adjusted as well.
+=== Push To Mirrors  ===
+Used <code>mirrorpush.sh</code> as documented in [[SeaMonkey:Release Process:2.0.3|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!
+* With the exception of the dropped locales like above, this is acceptable and will ship anyway.
+=== Push Updates to the beta Channel ===
+On aus |/opt/aus2/snippets/staging/|:
+ ~/bin/backupsnip Sea*2.1b3*build1
+ ~/bin/pushsnip Sea*2.1b3*build1
+== Build 2 ==
+Noticed that we bumped the WRONG version file, so had to do a build 2.
+Chmod aus updates to 700 so we don't auto-update anyone to broken b3. Did not backout any website changes or announcements. I hope to provide *real* auto-updates for this issue and announce it later.
+* Updated config: http://hg.mozilla.org/build/buildbot-configs/rev/97c2a97b74fd
+* Disabled updates (chmod 700 in |opt/aus2/incoming/3/seamonkey| for 2.1*)
+* Clobbered release dirs.
+* Kicked off with the following command:
+ buildbot sendchange --username=Callek --master=localhost:9010 --branch=comm-central -c "SeaMonkey 2.1b3build3" doit
+After builds were all in noticed that we didn't bump the version for build 2 (Which is normal for build>1) so I updated it myself manually, and did a build3
+== Build 3 ==
+* Updated configs for new c-c cset (left other repos alone)
+* Clobbered release dirs.
+* Kicked off with the following command:
+ buildbot sendchange --username=Callek --master=localhost:9010 --branch=comm-central -c "SeaMonkey 2.1b3build3" doit
+* Had many locale failures on the windows repacks, due to hg timeouts. I clobbered all those machines, and found a list of locales we were missing.
+* Found http://hg.mozilla.org/build/tools/file/8e1cd38b7bc8/buildbot-helpers/force_release_l10n.py which I skimmed code path to see if it would work, noticed that force-build wouldn't, so created a user repo and patch it so it works with a 0.8 based buildbot ([http://hg.mozilla.org/users/Callek_gmail.com/tools/rev/43ab69477079 1])
+* Created a locale list, citing only windows, and ran the forcer (See [[ SeaMonkey:Release_Process:2.1b3/Logs/Build3_Repack_Force|Log]])
+** One locale still failed from a timeout, manually hit <code>rebuild</code> on buildbot waterfall
+=== Fake tr locale ===
+In order for bouncer/sentry to see our files, I created fake tr locale files on ftp:
+ mkdir "win32/tr" "linux-i686/tr" "mac/tr"
+ mkdir "update/win32/tr" "update/linux-i686/tr" "update/mac/tr"
+ touch "win32/tr/SeaMonkey Setup 2.1 Beta 3.exe" \
+ "linux-i686/tr/seamonkey-2.1b3.tar.bz2" \
+ "mac/tr/SeaMonkey 2.1 Beta 3.dmg" \
+ "update/win32/tr/seamonkey-2.1b3.complete.mar" \
+ "update/linux-i686/tr/seamonkey-2.1b3.complete.mar" \
+ "update/mac/tr/seamonkey-2.1b3.complete.mar"
 === Signing ===
-* TBD manually via fakesign.sh
+* 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.
+** This time I created a mac64tomac.sh script following the setup above, I ran this script
+* 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 <code>sh ~/fakesign.sh</code>
+=== Updates and Verification ===
+*_l10n_verify and updates started automatically, triggered by the fake-signing.
+** L10n verification is mostly useless, since we have many new locales, and lots of expected changed strings.
+* update completed fine
+** the Update verification was red for all platforms, due to the dropping of 4 locales that were in b2: ''`it`'', ''`fi`'', ''`nb-NO`'', ''`sv-SE`''. This is ok in this case. Everything else was fine.
+=== 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.
+=== Zipcopy ===
+Used <code>zipcopy.sh</code> as documented in [[SeaMonkey:Release_Process:2.0b1|2.0b1]] notes to move the Windows zips into the directory we want them in for release.
+=== Create Checksums ===
+With <code>make-checksums.sh</code> as documented in [[SeaMonkey:Release_Process:2.0.3|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.
+* I set the Checksum script to copy the README from the 2.1b3 release previously pushed, since I already updated that one.
+=== Push To Mirrors  ===
-=== Verification ===
+Created <code>mirrorpush-new.sh</code> so that we push this Build to |2.1b3-real| like was done in [[Firefox_3.0.19/BuildNotes]] so we can have the mirrors properly uptake this.
-* linux_l10n_verification:
-* win32_l10n_verification:
-* macosx_l10n_verification:
-* linux_update_verify:
-* win32_update_verify:
-* macosx_update_verify:
-* final_verification:
-=== Update Channels ===
+=== Update Bouncer for 2.1b3-real ===
-* Push to beta:
+Filed {{bug|648775}} for the bouncer updates. Nthomas was great to fix that fast.
-* Push to mirrors:
-* Push to release: