Releases/Firefox 35.0.1/BuildNotes: Difference between revisions
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
=== Update verify / QE update test failures === | === 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). | 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). | ||
== Shipping == | |||
'''When shipping, the whatsnew rule for the release channel needs to be updated by hand in addition to running the update shipping builder and pushing snippets''' | |||
Revision as of 16:00, 23 January 2015
Build 1
Checklist
(RelMan) Ship the l10n milestone- (RelMan) Submit to Ship It
Set up whatsnew page- Push to mirrors
- Apply Throttling
- Verify throttling
- Run pushsnip
- Publish in Balrog
- Post-release tasks
- Mark as shipped
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).
Shipping
When shipping, the whatsnew rule for the release channel needs to be updated by hand in addition to running the update shipping builder and pushing snippets