352
edits
(→Process: release criteria) |
(→Release Criteria: add link) |
||
Line 59: | Line 59: | ||
* QA will run the regression test suite, updated with the coverage for new features, and inform the Dev team with any findings. | * QA will run the regression test suite, updated with the coverage for new features, and inform the Dev team with any findings. | ||
* During triage, it will be decided that whether a found issue is a release blocker or not. As a minimum, a bug shall be a release blocker if it causes crash/hang on a relatively common use case scenario. The Dev team will provide fix for the release blockers during the code freeze, and the fix will be verified. | * During triage, it will be decided that whether a found issue is a release blocker or not. As a minimum, a bug shall be a release blocker if it causes crash/hang on a relatively common use case scenario. The Dev team will provide fix for the release blockers during the code freeze, and the fix will be verified. | ||
* QA will sign off the release when the (up-to-date) regression test suite run has been completed, and there are no release blockers. | * QA will sign off the release when the (up-to-date) regression test suite run has been completed, all items under [[#Test_Deliverables|Test_Deliverables]] has been completed, and there are no release blockers. | ||
== Manual Tests == | == Manual Tests == |
edits