Procedure of bugfixes and features

Here is the testing process proposal for this project (Code is merged in pull requests only, so testers only need to test "pull request"):

1. Developers add label "verification-needed" in pull request which are ready for testing.
2. Developers link issues which are to be fixed in the pull request.
3. Developers change assignee to Lihua Liu and Sonny William in the pull request.
4. Lihua and Sonny will decide which team works on the pull request testing and assign it to the correct tester.
5. Developers or testers add acceptance criteria tests in the pull request and start testing. Testers remove label "verification-needed" and add label "testing" in pull request.

• a. If the issues are fixed in topic branch code, testers approve the pull request. Testers remove label "testing" and add label "test complete", then change assignee to developer.
• b. If the issues are not fixed in topic branch code, testers add comments in the pull request. Testers wait for developer's investigation and retest updated topic branch build. Once all the issues are fixed in new topic branch build, testers approve the pull request. Testers remove label "testing" and add label "test complete", then change assignee to developer.

6. Developers merge code to master branch and change assignee to tester.
7. Testers verify the pull request in master branch.

• a. If the issues are really fixed in master branch, testers remove label “test complete” and add label "verified" in pull request.
• b. If the issues still exist, testers update the pull request comments. Testers remove label “test complete” and add label "verified" in the pull request.

8. After the version is published, testers close the fixed issues and add "release" in thse issues. Please note testers DO NOT close the issues which are not fixed in step #7.b. Those issues need to be fixed in other pull requests in future verions.