At release v0.5.3 I noticed some issues in the protocol which should be solved.

• add info on credentials for test.pypi.org (step 9)
• add "Fixed" to unreleased section of changelog.md
• [decision wanted] release candidates and upload on test.pypi.org necessary?
• [decision wanted] versioning after release candidates that had failed
• add test for creating report

About [decision wanted] test.pypi.org: To my mind we can skip this step. The purpose of the release candidates is to check if the package is fine. Why would we need another test with test.pypi.org afterwards? If we want to keep it, I would at least place it before uploading rc1 to pypi as this might reduce the number of release candidates.

About [decision wanted] versioning: It came to my mind that if e.g. v0.6.0rc1 has errors that we fix, v0.6.0rc2 is different from thev0.6.0 tag on github. So this would mean that we should test release candidates before the github release..?!