Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
1,529
edits
SeaMonkey:Release Process:2.1b2: Difference between revisions
SeaMonkey:Release Process:2.1b2 (view source)
Revision as of 04:32, 6 February 2011
, 6 February 2011→Notes
(→Build) |
(→Notes) |
||
| Line 35: | Line 35: | ||
buildbot sendchange --username=Callek --master=localhost:9010 --branch=comm-central -c "SeaMonkey 2.1b2build1" doit | buildbot sendchange --username=Callek --master=localhost:9010 --branch=comm-central -c "SeaMonkey 2.1b2build1" doit | ||
* Forgot to clobber release dirs... so had to kick this again | * Forgot to clobber release dirs... so had to kick this again | ||
* Mac repacks, uploaded to "mac64" instead of "mac" along with their [complete] updates and xpi's, I filed {{bug|631864}} and manually moved all files to "mac" and moved on. | |||
=== Signing === | |||
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>fakesign.sh</code> as documented in [[SeaMonkey:Release_Process:2.1b1|2.1b1]] notes. | |||
<!-- | |||
=== Updates and Verification === | |||
* *_l10n_verify and updates started automatically, triggered by the fake-signing. | |||
** updates worked fine and reported green. | |||
** L10n verification is useless, as the previous release didn't have locales to compare with. | |||
* *_update_verify are all looking good for partials and bad for complete updates, but we verified by manual testing on betatest that complete updates work correctly. | |||
--> | |||
== Wall Clock Time == | == Wall Clock Time == | ||