Releases/Firefox 35.0.1/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "== Release == * <s>(RelMan) Ship the l10n milestone * (RelMan) Release:Release_Automation_on_Mercur...")
 
No edit summary
Line 1: Line 1:
== Release ==
= Build 1 =
== Checklist ==
* <s>(RelMan) [[Release:Release_Automation_on_Mercurial:Preparation#L10N_Changesets | Ship the l10n milestone]]
* <s>(RelMan) [[Release:Release_Automation_on_Mercurial:Preparation#L10N_Changesets | Ship the l10n milestone]]
* (RelMan) [[Release:Release_Automation_on_Mercurial:Starting_a_Release#Submit_to_Ship_It | Submit to Ship It]]
* (RelMan) [[Release:Release_Automation_on_Mercurial:Starting_a_Release#Submit_to_Ship_It | Submit to Ship It]]
Line 11: Line 12:
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Mark_release_as_shipped | Mark as shipped ]]
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Mark_release_as_shipped | Mark as shipped ]]


== Build 1 ==
== Issues ==
=== Mac partner repacks failed ===
Mac partner repacks failed multiple times due to {{bug|1008052}}. Worked on the third attempt. (We should really do something about this bug, or at least be able to retry on a different signing server.)
 
=== Update verify / QE update test failures ===
Some of our update verify tests as well as QE ones failed because the release-localtest channel was pointing at the Firefox-35.0-build3-whatsnew blob. To fix, bhearsum created a Firefox-35.0.1-build1-whatsnew blob and pointed the test channels at it. We may want to consider not enabling the whatsnew page for the localtest channels from now on, otherwise update verify will fail whenever we need a whatsnew page (because it triggers automatically after updates are published, leaving us precious little time to create the whatsnew blob before they run).

Revision as of 15:53, 23 January 2015

Build 1

Checklist

Issues

Mac partner repacks failed

Mac partner repacks failed multiple times due to bug 1008052. Worked on the third attempt. (We should really do something about this bug, or at least be able to retry on a different signing server.)

Update verify / QE update test failures

Some of our update verify tests as well as QE ones failed because the release-localtest channel was pointing at the Firefox-35.0-build3-whatsnew blob. To fix, bhearsum created a Firefox-35.0.1-build1-whatsnew blob and pointed the test channels at it. We may want to consider not enabling the whatsnew page for the localtest channels from now on, otherwise update verify will fail whenever we need a whatsnew page (because it triggers automatically after updates are published, leaving us precious little time to create the whatsnew blob before they run).