1,457
edits
Samuelsidler (talk | contribs) (New page: This is the general release checklist we should use for maintenance releases. We use this checklist to make sure we don't miss any community, development, QA, Build, Product team, or partn...) |
Samuelsidler (talk | contribs) |
||
| Line 34: | Line 34: | ||
** Email betatesters when builds are created - <font color="blue">Project lead</font> | ** Email betatesters when builds are created - <font color="blue">Project lead</font> | ||
* | * QA verification - <font color="orange">QA Lead</font> | ||
** Complete Bug Verification Target - <font color="orange">QA Lead</font> | ** Complete Bug Verification Target - <font color="orange">QA Lead</font> | ||
** BFT on one platform - <font color="orange">QA Lead</font> | ** BFT on one platform - <font color="orange">QA Lead</font> | ||
* Complete Regression Testing - <font color="orange">QA Lead</font> | ** Complete Regression Testing - <font color="orange">QA Lead</font> | ||
** Examples: All BFTs/FFTs, JS regression test, Security regression test, top sites, top extensions, etc. See Test Plan for details. | *** Examples: All BFTs/FFTs, JS regression test, Security regression test, top sites, top extensions, etc. See Test Plan for details. | ||
** en-US Install/start page/Version ID/Update test - <font color="orange">QA Lead</font> | |||
| Line 44: | Line 47: | ||
^ I'm to here with updating | ^ I'm to here with updating | ||
* L10n | * L10n | ||
edits