ReleaseEngineering/Planning: Difference between revisions

no edit summary
(reconfig)
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 13: Line 13:
* [[Version Control System]]
* [[Version Control System]]
* [[Build:Release Automation|Release Automation]]
* [[Build:Release Automation|Release Automation]]
= Reconfigs / Deployments =
This page is updated by the person who does a [[ReleaseEngineering:Buildduty:Reconfigs|reconfig]] on production systems. Please give accurate times, as we use this page to track down if reconfigs caused debug intermittent problems. (This includes config changes not requiring a "reconfig", such as <i>mozharness</i> changes.)
Outcome should be 'backed out' or 'In production' or some such. Reverse date order pretty please.
Older changes are archived in: [[ReleaseEngineering/Changes/2013|2013]] | [[ReleaseEngineering/Changes/2012|2012]] | [[ReleaseEngineering/Changes/2011|2011]] | [[ReleaseEngineering/Changes/2010|2010]] | [[ReleaseEngineering/Changes/2009|2009]]
{| class="fullwidth-table sortable"
| style="background:#cccccc" | '''Outcome'''
| style="background:#cccccc" | '''When'''
| style="background:#cccccc" | '''Bug #(s)''' - '''Description(s)'''
|-
| in production
| 2014-03-04 11:28 ET
|
* coop is testing
|-
| in production
| 2014-03-03 10:20 PT
|
* {{bug|977579}} - Please schedule linux jit-tests in two chunks; r=jlund <- mozharness
* {{bug|978233}} - emulator-jb should use --manifest instead of --test-manifest, r=jgriffin <- mozharness
|}
canmove, Confirmed users
2,850

edits