Releases/Firefox 37.0/BuildNotes: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 53: Line 53:
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Set-up_whatsnew_page | Set up whatsnew page]]
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Set-up_whatsnew_page | Set up whatsnew page]]
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Publish_in_Balrog | Publish RC to Beta channel]]
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Publish_in_Balrog | Publish RC to Beta channel]]
* [[Release:Release_Automation_on_Mercurial:Updates#Push_to_mirrors | Push to mirrors]]</s>
* [[Release:Release_Automation_on_Mercurial:Updates#Push_to_mirrors | Push to mirrors]]
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Do_I_need_to_throttle.3F | Apply Throttling ]]
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Do_I_need_to_throttle.3F | Apply Throttling ]]
* [[Release:Release_Automation_on_Mercurial:Updates#Verifying_Throttling | Verify throttling ]]
* [[Release:Release_Automation_on_Mercurial:Updates#Verifying_Throttling | Verify throttling ]]
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Publish_in_Balrog | Publish in Balrog ]]
* Publish by hand</s>
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Post-release_tasks | Post-release tasks]]
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Post-release_tasks | Post-release tasks]]


Line 71: Line 71:
=== Manually force "ready for beta-cdntest" and "beta final verification" builders ===
=== Manually force "ready for beta-cdntest" and "beta final verification" builders ===
A (new and different) error in the patch from {{bug|1105485}} caused these not to fire automatically. They had to be forced again. The release equivalents will need forcing too, but not until after we push to mirrors.
A (new and different) error in the patch from {{bug|1105485}} caused these not to fire automatically. They had to be forced again. The release equivalents will need forcing too, but not until after we push to mirrors.
=== Publish by hand ===
For this release, the "default" rule in Balrog had to be pointed at the no-whatsnew blob, so we couldn't use the "update shipping" builder. To publish, did the following:
* Created a new rule for the whatsnew locales by duplicating the release-cdntest one and adjusting the channel. It had the following data:
** Product: Firefox
** Channel: release
** Mapping: Firefox-37.0-build2
** Rate: 25
** Priority: 91
** Locale: en-US,en-GB,de,pt-BR,id,fr,es-ES,es-MX
Then I deleted the rule that was in place for 36.0 whatsnew pages. Finally, repointed the "default" Firefox release channel rule to the Firefox-37.0-build2-no-whatsnew blob and changed its rate to 25%. Any locales not included in the newly created rule above will fall through to it.
The order of operations is important here -- if the "default" rule was updated before the new one was created some users on the listed locales would not have received a whatsnew page.


= Fennec =
= Fennec =
canmove, Confirmed users
6,441

edits

Navigation menu