Socorro/Release Process: Difference between revisions
< Socorro
Jump to navigation
Jump to search
(quick outline) |
(typo) |
||
| Line 5: | Line 5: | ||
== Code freeze == | == Code freeze == | ||
* code is branched per https://wiki.mozilla.org/Socorro/Release_Branch_Strategy | * code is branched per https://wiki.mozilla.org/Socorro/Release_Branch_Strategy | ||
* staging data is refreshed and new build is loaded to branch staging server (crash-stats.allizom. | * staging data is refreshed and new build is loaded to branch staging server (crash-stats.allizom.org) | ||
== Verification == | == Verification == | ||
Revision as of 19:41, 29 June 2011
New feature/bugfix
- Socorro bugs are triaged and "Target Milestone" field in bugzilla is set
- As bugs are resolved, QA verifies them against the trunk staging server (crash-stats-dev.allizom.org)
Code freeze
- code is branched per https://wiki.mozilla.org/Socorro/Release_Branch_Strategy
- staging data is refreshed and new build is loaded to branch staging server (crash-stats.allizom.org)
Verification
- QA verifies fixes against branch staging server
- Socorro devs verify logs on each server:
- /var/log/socorro/*.log
- /var/log/socorro/kohana/*.php
- Socorro devs verify logs on each server:
Push to production
- When QA signs off, a push bug in mozilla.org/Server Ops
- for example see: bug 667819
- Socorro devs verify logs on each server:
- /var/log/socorro/*.log
- /var/log/socorro/kohana/*.php