Ottehr Release Checklist Draft

Early Release Responsibilities:

[x] Choose a name for the release
[x] Create a new milestone for the release. If one already exists, rename it to the release's name
[x] Create a new milestone for the next release
This will be useful if you want to delay any tickets for future releases.
For now, it can be named as just the next letter in the release alphabet. So if your release is "Cat", call the next milestone "D"
[x] Create a project board for the release. Name is the release name and filter tickets by milestone:release_name.
[x] Choose a set of tickets to include in the release, assign them to the release and set their status to To Do
[x] Assign someone to each ticket, make sure they are aware of when you expect the ticket to be done
[x] Find a tester for each ticket

Mid Release Responsibilities:

[ ] Follow up with people about their tickets. Will they be done in time? Will they need to be pushed to the next release?
Make sure their statuses are up to date. If not, ask the ticket assignee to update the status.
If they need to be pushed, move them to the next release and explain to any stakeholders why the ticket is being pushed.
[ ] Make sure all PRs that need to be reviewed are reviewed
[ ] Code freeze by Thursday

Late Release Responsibilities:

[ ] Ensure all tickets are completed and being tested
[ ] Follow up with testers to confirm that they will have time to test their tickets before the release. If not, find a new tester
[ ] Draft release notes for the release
[ ] Create a new Oystehr account to use later when testing new project setup in the release

Pre-release Responsibilities:

Release

Post-release Responsibilities:

masslight / ottehr