SeaMonkey:Release Process:2.1b3: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 105: Line 105:
Noticed that we bumped the WRONG version file, so had to do a build 2.
Noticed that we bumped the WRONG version file, so had to do a build 2.


clobbered release dirs, fell asleep. 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.
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
* Updated config: http://hg.mozilla.org/build/buildbot-configs/rev/97c2a97b74fd
* Disabled updates (chmod 700 in |opt/aus2/
* 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


== Wall Clock Time ==
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 ===
== Build 3 ==
* buildbot sendchange: Tue Apr  5 22:24:52 PDT 2011
* tag:
* source:
* linux_build:
* linux64_build:
* win32_build:
* macosx_build:
* linux_repack (12 locales):
* win32_repack (12 locales):
* macosx_repack (12 locales):
* signing:
**''Start'': Wed Apr 6 12:29:47 PDT 2011
**''End'': Wed Apr 6 12:30:09 PDT 2011
* updates:


=== Verification ===
* Updated configs for new c-c cset (left other repos alone)
* linux_l10n_verification:
* Clobbered release dirs.
* win32_l10n_verification:
* Kicked off with the following command:
* macosx_l10n_verification:
buildbot sendchange --username=Callek --master=localhost:9010 --branch=comm-central -c "SeaMonkey 2.1b3build3" doit
* linux_update_verify:
* win32_update_verify:
* macosx_update_verify:
* final_verification:


=== Update Channels ===
* 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


* Push to beta:
=== Fake tr locale ===
* Push to mirrors:
In order for bouncer/sentry to see our files, I created fake tr locale files on ftp:
* Push to release:
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 ===
 
* 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  ===
 
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#Push_to_mirrors_.28again.29]] so we can have the mirrors properly uptake this.
 
=== Update Bouncer for 2.1b3-real ===
 
Filed {{bug|648775}} for the bouncer updates. Nthomas was great to fix that fast.
Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
1,529

edits