Releases/Firefox 14.0b11/BuildNotes: Difference between revisions

Releases/Firefox 14.0b11/BuildNotes (view source)

Revision as of 17:26, 10 July 2012

12 bytes removed , 10 July 2012

m

→‎Firefox

Kmoir

Confirmed users

1,989

edits

@@ Line 100: / Line 100: @@
   PYTHONPATH=. python ../tools/buildbot-helpers/release_sanity.py -u kmoir -V 14.0b11 --branch mozilla-beta --build-number 1     --release-config release-firefox-mozilla-beta.py --release-config release-fennec-mozilla-beta.py --products firefox,fennec  localhost:9001
-The release emails indicated that the Fennec build being created was 14.0b2 which was completely unexpected.  After talking with rail, callek, bhearsum and catlee, they determined that the problem was that bm12 took the Fennec build instead of bm13 and it was pointing to mozilla-beta since the 14.0 release was run from mozilla-beta.  The sendchange to so the trigger 14.0b11 builds also triggered 14.0 build2 again.  The fennec release configs point to mozilla-beta, so they advised me to change release-fennec-mozilla-release.py to point to mozilla-release, land in production, retag the buildbot-configs, reconfig bm12 and bm13 and trigger the Fennec build again.
+The release emails indicated that the Fennec build being created was 14.0b2 which was completely unexpected.  After talking with rail, callek, bhearsum and catlee, they determined that the problem was that bm12 took the Fennec build instead of bm13 and it was pointing to mozilla-beta since the 14.0 release was run from mozilla-beta.  The sendchange to trigger 14.0b11 builds triggered 14.0 build2 again.  The fennec release configs point to mozilla-beta, so they advised me to change release-fennec-mozilla-release.py to point to mozilla-release, land in production, retag the buildbot-configs, reconfig bm12 and bm13 and trigger the Fennec build again.
 I started the Fennec build with the following command after running a successful release sanity.