Releases/Firefox 36.0.3/BuildNotes: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 6: Line 6:
* [[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#Push_to_mirrors | Push to mirrors]]</s>
* [[Release:Release_Automation_on_Mercurial:Updates#Push_to_mirrors | Push to mirrors]]</s>
* [[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_through_Shipping#Publish_in_Balrog | Publish in Balrog ]]
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Publish_in_Balrog | Publish in Balrog ]]
* [[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 38: Line 36:
=== Manually force release-cdntest builder ===
=== Manually force release-cdntest builder ===
Had to manually force the release-cdntest testing builder to get that e-mail to be sent. Couldn't figure out why.
Had to manually force the release-cdntest testing builder to get that e-mail to be sent. Couldn't figure out why.
=== Publish on release channel ===
'''NOT DONE YET!'''
In addition to running the "update shipping" builder, the version>=36.0, channel=release rule needs to be updated in Balrog to point at Firefox-36.0.3-build1-no-whatsnew


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

edits