Release:Release Automation on Mercurial:Documentation: Difference between revisions

Release:Release Automation on Mercurial:Documentation (view source)

754 bytes added , 19 November 2010

canmove, Confirmed users

6,441

edits

@@ Line 294: / Line 294: @@
 === Signing ===
-This is a semi-automated process, and should be done with [https://intranet.mozilla.org/Build:CombinedSigning this] document.
+Code used:
+* [http://hg.mozilla.org/build/tools/file/tip/release/signing/Makefile Signing Makefile]
+* [http://hg.mozilla.org/build/tools/file/tip/release/signing/sign-release.py sign-release.py]
+* sign-release (no link available)
+* sign-files (no link available)
+* verify-signatures (no link available)
+* checksum-files (no link available)
-An FtpPoller watches for the signing log to appear on the ftp server and triggers the next group of steps.
+Deliverables:
+* Signed Windows builds (internal binaries and installers), including partner repacks (where applicable)
+* Detached GPG signatures for all builds and source packages
+* MD5SUMS and SHA1SUMS files containing checksums for all builds, source packages, langpacks, and some MARs
+This is a semi-automated process. The instructions for initiating and finishing the process are documented on [https://intranet.mozilla.org/Build:CombinedSigning the Combined Signing page].
+The final step of signing is uploading the signing log. An FtpPoller watches for it to appear on the ftp server and triggers the appropriate builders when it appears.
 === L10n Verify ===