aaron/mattermost-desktop
1
0
Fork 0
Code Issues Pull requests Actions 2 Packages Projects Releases Wiki Activity

Update release-process.md

Browse source
This commit is contained in:
Jason Blais 2017-01-01 21:09:49 -05:00 committed by GitHub
parent 5b70a1ce32
commit dec18ca54b
1 changed files with 11 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
docs/release-process.md
View file

@ -12,13 +12,16 @@ Notes:
Pre-work for the current release begins at the code complete date of the previous release. See "Code Complete" section below for details. Pre-work for the current release begins at the code complete date of the previous release. See "Code Complete" section below for details.
### B. (T-minus 12 working days) Cut-off for merging major features ### B. (T-minus 20 working days) Release Announcement
No pull requests for major features should be **merged** to the current release after this date
1. PM: 1. PM:
- Post this checklist in Desktop App channel - Post this checklist in Desktop App channel
- Confirm date of marketing announcement for the release and update Desktop App channel header if needed - Confirm date of marketing announcement for the release and update Desktop App channel header if needed
- Create meta issue for release in GitHub to let contributors and users know about the upcoming release. See [example issue](https://github.com/mattermost/desktop/issues/271).
- Prepare JIRA tickets for the next release, with a corresponding vX.X prefix
- Cut the release candidate (RC1)
- Cut final release with code-signing for Windows and Mac builds
- Queue desktop app for a 15-minute team testing
2. Dev/PM: 2. Dev/PM:
- Prioritize reviewing, testing, and merging of pull requests for current release until there are no more tickets in the [pull request queue](https://github.com/mattermost/desktop/pulls) marked for the current release - Prioritize reviewing, testing, and merging of pull requests for current release until there are no more tickets in the [pull request queue](https://github.com/mattermost/desktop/pulls) marked for the current release
@ -33,7 +36,7 @@ No pull requests for major features should be **merged** to the current release
- Coordinate testing: - Coordinate testing:
- Update the RC Testing Spreadsheet to cover any changes or new features, confirm that known issues are listed in the relevant tests, and assign each area to a team member - Update the RC Testing Spreadsheet to cover any changes or new features, confirm that known issues are listed in the relevant tests, and assign each area to a team member
- Post in Desktop App channel alerting community of upcoming release and to ask help with testing the release candidate - Post in Desktop App channel alerting community of upcoming release and to ask help with testing the release candidate
- Create meta issue for release in GitHub with a link to the changelog - Update meta issue for release in GitHub with a link to the changelog
2. Dev/PM: 2. Dev/PM:
- Submit changelog with updates for improvements, bug fixes, known issues, and contributors - Submit changelog with updates for improvements, bug fixes, known issues, and contributors
- Finalize roadmap for next release - Finalize roadmap for next release
@ -67,8 +70,10 @@ No pull requests for major features should be **merged** to the current release
1. PM: 1. PM:
- Post this checklist in Desktop App channel - Post this checklist in Desktop App channel
- Verify all items in the last posted release checklist are complete - Verify all items in the last posted release checklist are complete
- Check that known issues section of Changelog is updated - Check that the following are updated in the Changelog:
- Check that the contributors section of Changelog is updated - Known issues
- Contributors
- Release candidate bug reports
2. Dev/PM: 2. Dev/PM:
- Finish assigned areas of the Release Candidate Testing spreadsheet - Finish assigned areas of the Release Candidate Testing spreadsheet
- Continue triaging hotfix candidates and decide on whether and when to cut next RC or final - Continue triaging hotfix candidates and decide on whether and when to cut next RC or final