ReleaseEngineering/Planning: Difference between revisions
Jump to navigation
Jump to search
Warning: This RelEng page is obsolete! Not updated since 2010
ChrisCooper (talk | contribs) (reconfig) |
ChrisCooper (talk | contribs) (reconfig) |
||
| Line 25: | Line 25: | ||
| style="background:#cccccc" | '''When''' | | style="background:#cccccc" | '''When''' | ||
| style="background:#cccccc" | '''Bug #(s)''' - '''Description(s)''' | | style="background:#cccccc" | '''Bug #(s)''' - '''Description(s)''' | ||
|- | |||
| in production | |||
| 2014-03-04 11:28 ET | |||
| | |||
* coop is testing | |||
|- | |- | ||
| in production | | in production | ||
Revision as of 17:21, 4 March 2014
Planning
Old
These are plans that have been executed (which can mean "completed" or or "killed", I suppose!)
- Blogging blitz
- PyCon 2010
- Try Server Suggestions
- Configure System Rewrite
- Stage Migration Notes
- Version Control System
- Release Automation
Reconfigs / Deployments
This page is updated by the person who does a 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 mozharness changes.)
Outcome should be 'backed out' or 'In production' or some such. Reverse date order pretty please.
Older changes are archived in: 2013 | 2012 | 2011 | 2010 | 2009
| Outcome | When | Bug #(s) - Description(s) |
| in production | 2014-03-04 11:28 ET |
|
| in production | 2014-03-04 11:28 ET |
|
| in production | 2014-03-03 10:20 PT |
|