Confirmed users
927
edits
Services/Process/ServerReleaseProcess: Difference between revisions
→Hand off from Engineering to Test Checklist
mNo edit summary |
Tarek.ziade (talk | contribs) |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 4: | Line 4: | ||
= Sequence of events = | = Sequence of events = | ||
== Weekly == | == Weekly == | ||
* '''Tuesday''' - Features going into that week's push are determined at the [[Services/Meetings|Services Weekly Meeting]]. A drop to Test will be made by EOB Tuesday. | * '''Tuesday''' - Features going into that week's push are determined at the [[Services/Meetings|Services Weekly Meeting]]. If changes need a public announcement, Services Ops will call that out in the meeting. | ||
* '''Wednesday''' - A drop to Test will be made by EOB Tuesday. | |||
* '''Friday''' - Test will sign off by EOB | * '''Friday''' - Test will sign off by EOB | ||
* '''Monday''' - Production pushes will be done every Monday in the evening. The maintenance window is 3 - 5 PM PST. | * '''Monday''' - Production pushes will be done every Monday in the evening. The maintenance window is 3 - 5 PM PST. | ||
== Monthly == | == Monthly == | ||
* For resource planning, there will be a monthly meeting with security (other groups too perhaps) to go over the up coming month's work. (jarguello will add this link) | * For resource planning, there will be a monthly meeting with security (other groups too perhaps) to go over the up coming month's work. (jarguello will add this link) | ||
| Line 12: | Line 14: | ||
= Hand off from Engineering to Test Checklist = | = Hand off from Engineering to Test Checklist = | ||
* A tag with changes | * A tag with changes | ||
* A healthy Jenkins status for the project (blue and sunny) | |||
* A test plan for changes (Template of this coming soon) | * A test plan for changes (Template of this coming soon) | ||
* Security Documentation Update and Security Sign Off (If necessary) | * Security Documentation Update and Security Sign Off (If necessary) | ||
* Dev will file deploy bugs with any special instructions for service ops. | * Dev will file deploy bugs with any special instructions for service ops. | ||
* Dev will send e-mail to services-qa@mozilla.com with the buglist, test plan link, location of staging environment and staging database | * Dev will send e-mail to: services-qa@mozilla.com cc: services-ops@mozilla.com with the buglist, test plan link, location of staging environment and staging database | ||
* Service Ops will push to staging. | * Service Ops will push to staging. | ||
* NOTE: staging environment and staging database need to be stable during testing period. Otherwise, please notify Test by sending a notification e-mail to services-qa@mozilla.com | * NOTE: staging environment and staging database need to be stable during testing period. Otherwise, please notify Test by sending a notification e-mail to services-qa@mozilla.com | ||
| Line 23: | Line 26: | ||
* QA regression tests pass | * QA regression tests pass | ||
* cross environment tests pass | * cross environment tests pass | ||
* Test plan passes | * [https://wiki.mozilla.org/QA/Sync/Test_Plan#Servers Test plan] passes | ||
* Service Ops signs off on any load testing if necessary | * Service Ops signs off on any load testing if necessary (is this in stage or production environments?) | ||
* Test sends e-mail notification to services-qa@mozilla.com with results | * Test sends e-mail notification to services-qa@mozilla.com with results | ||