Confirmed users
107
edits
QA/BrowserID/BrowserID Weekly Trains Beta: Difference between revisions
QA/BrowserID/BrowserID Weekly Trains Beta (view source)
Revision as of 20:49, 6 December 2012
, 6 December 2012no edit summary
No edit summary |
|||
| Line 59: | Line 59: | ||
== Schedules == | == Schedules == | ||
* BrowserID testing runs on a bi-monthly "train" or schedule: | * BrowserID testing runs on a bi-monthly "train" or schedule: | ||
** Wednesday afternoon: deployment of current train to Production | ** (Day 1 / Day 15) Wednesday afternoon: deployment of current train to Production | ||
** Thursday/Friday: open testing and experimentation on Dev environment | ** (Day 2-3) Thursday/Friday: open testing and experimentation on Dev environment | ||
** Friday afternoon: deployment of next train to Stage | ** (Day 3) Friday afternoon: deployment of next train to Stage | ||
** Following week: Monday - Friday: QA testing | ** (Day 6-10) Following week: Monday - Friday: QA testing | ||
** Third week: Monday - Tuesday: Final QA testing and sign off of current deployment | ** (Day 13-14) Third week: Monday - Tuesday: Final QA testing and sign off of current deployment | ||
* NOTE: Dev deployments are now back in the hands of the Dev team, so they can control incremental builds and releases. | * NOTE: Dev deployments are now back in the hands of the Dev team, so they can control incremental builds and releases. | ||
* NOTE 2: OPs is working on a Test/CI environment that will be deployed nightly for Dev and QA testing purposes (automation, etc.). | * NOTE 2: OPs is working on a Test/CI environment that will be deployed nightly for Dev and QA testing purposes (automation, etc.). | ||