Update release testing process

Jonathan Lange
2016-08-19 12:12:44 +01:00
parent af15ca4de1
commit a7d392fa30
+14 -2
@@ -60,8 +60,20 @@ git log --oneline latest_release...HEAD | \
Then sort the lines by feature, bug fix, performance etc. sections.
You may find it helpful to look at the original issues of the PRs to see what they are about.
Commit and push the CHANGELOG to the release branch.
Also, load the release branch on your test machines, and click around.
Only proceed from here once you have a few LGTMs.
## Test the release
* Create a PR for the release branch, merging into `master`
* For the description of the PR, supply a GFM checklist of things that need to be tested:
* if it's a major release, use the [Release Qualification] checklist
* if it's a patch release, make a list of things to be tested
Also, load the release branch on your test machines, and click around. If you discover any issues, or find yourself looking for anything in particular, update the [Release Qualification] checklist so we can get it deliberately next time.
Proceed from here only when:
* Every item on the checklist has been tested and confirmed to work
* The changelog has been reviewed and you have an LGTM
## Tag