Create a GitHub issue template for releases
rbreslow opened this issue · comments
Problem description
This came out of a meeting around https://github.com/azavea/raster-foundry-platform/issues/632.
The process to cut a release is loosely documented within the Release Workflow article on the deployment wiki.
Without something like a checklist, it's easy for people to forget certain steps in the release process. A checklist will reduce the stress and complexity of a release, because it enables you to spend less bandwidth worrying about completing the right steps. A checklist ensures your i's are dotted and t's crossed.
Expected Behavior or Output
To improve accountability, and deployment ergonomics, we should create a GitHub issue template for releases. The template will contain a checklist with all the steps involved in cutting a release.
Every future release should have an accompanying issue created, using the new template, and assigned to someone who "owns" that release.
If this new process works well, we should consider creating follow up issues to do the same for https://github.com/raster-foundry/raster-foundry, etc.
See: https://help.github.com/en/articles/creating-issue-templates-for-your-repository