Releases/Firefox 36.0.1/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎Checklist: ran postrelease)
 
(3 intermediate revisions by one other user not shown)
Line 4: Line 4:
* <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]]
* [[Release:Release_Automation_on_Mercurial:Updates_through_Shipping#Set-up_whatsnew_page | Set up whatsnew page]]</s>
* [[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#Push_to_mirrors | Push to mirrors]]
* [[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 ]]
* [[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]]</s>


=== Set up whatsnew page on release-cdntest ===
=== Set up whatsnew page on release-cdntest ===
Line 24: Line 23:


We'll need to create a similar rule for the "release" channel just before we ship.
We'll need to create a similar rule for the "release" channel just before we ship.
=== Apply throttling / ship to release channel ===
* Before triggering the "update shipping" builder, created a rule to handle whatsnew pages for the release channel. Same as above, except channel = "release".
* Triggered "update shipping" builder as usual
* Updated the main Firefox release channel rule to set background rate to 100% and remove comment about updates being shut off.


= Fennec =
= Fennec =

Latest revision as of 01:06, 6 March 2015

Firefox

Build 1

Checklist

Set up whatsnew page on release-cdntest

The whatsnew page for this release should only be shown for users coming from versions prior to 36.0. We'll need an extra rule in Balrog to accommodate this. This was done a little differently than the documentation shows because the automatically generated release blob already had the whatsnew page enabled. What I did was:

  • Create a new release called Firefox-36.0.1-build2-no-whatsnew, which is the same as the original blob but without "actions" or "openURL" in it.
  • Create a new rule with the following values:
    • product: Firefox
    • channel: release-cdntest
    • priority: 91
    • backgroundRate: 100
    • version: >=36.0
    • mapping: Firefox-36.0.1-build2-no-whatsnew

We'll need to create a similar rule for the "release" channel just before we ship.

Apply throttling / ship to release channel

  • Before triggering the "update shipping" builder, created a rule to handle whatsnew pages for the release channel. Same as above, except channel = "release".
  • Triggered "update shipping" builder as usual
  • Updated the main Firefox release channel rule to set background rate to 100% and remove comment about updates being shut off.

Fennec

Build 1

Checklist

Retrigger source tagging

en-US tagging failed before it pushed anything. Retriggered the job, but that didn't end up kicking downstream builders. Due to the way these schedulers work, I guess these aren't re-runnable. We decided to do a build2 instead of trying to kick it along by hand.

Build 2

Checklist