Confirmed users
632
edits
Loop/Load Handling: Difference between revisions
Jump to navigation
Jump to search
→Recommended Handling
| Line 79: | Line 79: | ||
'''Week of January 5''' - Leading up to the uplift of 35 to release, we again reduce the throttle to 10% ({{Bug|1118312}}). Note that the throttle acts as a ratchet: once active, the service remains active. Reducing the throttle will not cause the feature to disappear from 34 browsers. | '''Week of January 5''' - Leading up to the uplift of 35 to release, we again reduce the throttle to 10% ({{Bug|1118312}}). Note that the throttle acts as a ratchet: once active, the service remains active. Reducing the throttle will not cause the feature to disappear from 34 browsers. | ||
'''Approximately January 15 - February 15''' - Repeat the throttle increase process described above. | '''Approximately January 15 - February 15''' - Repeat the throttle increase process described above. (20%: January 22, {{Bug|1124908}}) | ||
'''Approximately February 15''' - {{Bug|1073218}} should land in Firefox 36, which will be in release around this date. We still want to give people time to upgrade before leaving users on 35 without a button in the default toolbar; one release cycle should be long enough. | '''Approximately February 15''' - {{Bug|1073218}} should land in Firefox 36, which will be in release around this date. We still want to give people time to upgrade before leaving users on 35 without a button in the default toolbar; one release cycle should be long enough. | ||