Releases/Firefox 3.0.19/BuildNotes: Difference between revisions

Releases/Firefox 3.0.19/BuildNotes (view source)

871 bytes added , 31 March 2010

canmove, Confirmed users

6,441

edits

@@ Line 313: / Line 313: @@
 ==== Post-Release Issues ====
 Because I missed a step in the signing of installers, namely SIGNING the win32 INSTALLERS, [https://bugzilla.mozilla.org/show_bug.cgi?id=556222 bug 556222] was filed and I signed the windows installers according to the steps in the [https://intranet.mozilla.org/Build:Signing#Installer.2Farchive_signing_before_release signing doc], then synched those newly signed win32 installers to the ftp release directory.
+The builds were pushed back to stage wrong, and ended up in /data/cltbld/firefox-3.0.19/stage-merged/win32/win32. They were then pushed to /releases/ wrong by doing:
+ rsync -av /data/cltbld/firefox-3.0.19/stage-merged/ /home/ftp/pub/firefox/releases/3.0.19/
+...which created a win32/win32 directory there, too.
+Fixed all of this by doing:
+ # cltbld @ stage
+ rsync -av /data/cltbld/firefox-3.0.19/stage-merged/win32/win32/ /home/ftp/pub/firefox/releases/3.0.19/win32/
+ rm -rf /data/cltbldl/firefox-3.0.19/stage-merged/win32/win32
+ rm -rf /home/ftp/pub/firefox/releases/3.0.19/win32/win32
+ rsync -av /data/cltbld/firefox-3.0.19/stage-merged/win32/ /home/ftp/pub/firefox/releases/3.0.19/win32/
+...and then we realized that we can't just override files on stage, because we can't guarantee that all of the mirrors will pick them up. The sections below track fixing that.
 ==== Push to mirrors (again) ====