Update release-process.md

doc/process/release-process.md

@@ -9,114 +9,148 @@ Notes:
 - T-minus counts are measured in "working days" (weekdays other than major holidays concurrent in US and Canada) prior to release day.
 
 ### (Code complete date of previous release) Beginning of release
-- 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.
 
 ### (T-minus 10 working days) Cut-off for major features
-- No pull requests for major features should be submitted to the current release after this date (except if release manager decides to add "release-exception" label)
+
-- (Ops) Post this checklist in Release channel 
+No pull requests for major features should be submitted to the current release after this date (except if release manager decides to add "release-exception" label to Jira ticket).
-- (PM) Write compatibility updates for config.json and database changes [See example](https://github.com/mattermost/platform/blob/master/CHANGELOG.md#compatibility)
+
-- (PM) Confirm changes to config.json in compatibility section of Changelog are written back to [settings documentation](https://github.com/mattermost/platform/blob/master/doc/install/Configuration-Settings.md)
+1. Ops:
-- (Dev) Prioritize reviewing, updating, and merging of pull requests for current release until there are no more tickets in the [pull request queue](https://github.com/mattermost/platform/pulls) marked for the current release 
+  1. Post this checklist in Release channel 
-- (Leads) Meets to prioritize the final tickets of the release
+2. PM:
-  - Backlog is reviewed and major features that won’t make it are moved to next release
+   1. Write compatibility updates for config.json and database changes [See example](https://github.com/mattermost/platform/blob/master/CHANGELOG.md#compatibility)
-  - Triage tickets
+  - Confirm changes to config.json in compatibility section of Changelog are written back to [settings documentation](https://github.com/mattermost/platform/blob/master/doc/install/Configuration-Settings.md)
-  - Finalize roadmap for next release
+ - Update [Upgrade Guide](https://github.com/mattermost/platform/blob/master/doc/install/Upgrade-Guide.md) for any steps needed to upgrade to new version
-  - Draft roadmap for release after next (used to prioritize design tasks)
+  - Prepare tickets for [cutting RC builds](https://mattermost.atlassian.net/browse/PLT-985), [creating the final release candidate](https://mattermost.atlassian.net/browse/PLT-986), [creating AMIs](https://mattermost.atlassian.net/browse/PLT-1213), and [testing GitLab RC with Mattermost](https://mattermost.atlassian.net/browse/PLT-1013)
-- (Marketing) Drafts marketing bullet points for next release based off of roadmap
+3. Dev:
-- (Marketing) Submits pull request for "Highlights" section of the Changelog
+  1. Prioritize reviewing, updating, and merging of pull requests for current release until there are no more tickets in the [pull request queue](https://github.com/mattermost/platform/pulls) marked for the current release 
-- (Marketing) Notes date of announcements in release channel
+4. Leads: Meet to prioritize the final tickets of the release
  1. Backlog is reviewed and major features that won’t make it are moved to next release
-- (PM) Update [Upgrade Guide](https://github.com/mattermost/platform/blob/master/doc/install/Upgrade-Guide.md) for any steps needed to upgrade to new version
+  - Triage tickets
-- (PM) Prepare tickets for [cutting RC builds](https://mattermost.atlassian.net/browse/PLT-985), [creating the final release candidate](https://mattermost.atlassian.net/browse/PLT-986), [creating AMIs](https://mattermost.atlassian.net/browse/PLT-1213), and [testing GitLab RC with Mattermost](https://mattermost.atlassian.net/browse/PLT-1013)
+  - Finalize roadmap for next release
-- (Stand-up) Each team member discusses worst bug (10-15s)
+  - Draft roadmap for release after next (used to prioritize design tasks)
+5. Marketing:
+  1. Drafts marketing bullet points for next release based off of roadmap
+  - Submits pull request for "Highlights" section of the Changelog
+  - Notes date of announcements in release channel
+6. Team:
+  1. In Stand-up, each team member discusses worst bug (10-15s)
  
  ### (T-minus 8 working days) Feature Complete and Stabilization
-- No pull requests for features can be submitted to the current release after this date (except if release manager add "release-exception" label to Jira ticket)
+
-- (Ops) Post this checklist in Release channel 
+**Stablization** period begins when all features for release have been committed. During this period, only **bugs** can be committed to master. Non-bug pull requests are tagged for next version, and are not committed to master until after a release candidate is cut.
-- (Dev) Prioritize reviewing, updating, and merging of pull requests for current release until there are no more tickets in the [pull request queue](https://github.com/mattermost/platform/pulls) marked for the current release 
+
-- **Stablization** period begins when all features for release have been committed. 
+Exceptions can be made by the release manager setting priority to "Highest" and adding a "release-exception" label to the Jira ticket. This will add the ticket to the [hotfix list for release candidate](https://mattermost.atlassian.net/issues/?filter=10204).
-  - During this period, only **bugs** can be committed to master. Non-bug pull requests are tagged for next version and wait until after a release candidate is cut to be committed to master
+
-  - (RM) Exceptions can be made by release manager by setting priority to "Highest" and labelling "release-exception", which will add ticket to [Hotfix list for release candidate](https://mattermost.atlassian.net/issues/?filter=10204).
+1. Ops:
-  - (PM) Review all [Severity 1 bugs (data loss or security)](https://mattermost.atlassian.net/secure/IssueNavigator.jspa?mode=hide&requestId=10600) to consider for adding to Hotfix list. 
+  1. Post this checklist in Release channel
-- (PM) Complete documentation 
+  -  Update the channel header to reflect date
-  - (PM) Make Changelog PR with updates for latest feature additions and changes
+  - Mail out mugs to any new contributors
-  - (PM) Make Changelog PR with updates to contributors
+2. Dev:
-  - (PM) Make NOTICE.txt PR for any new libraries added from dev, if not added already 
+   1. Prioritize reviewing, updating, and merging of pull requests for current release until there are no more tickets in the [pull request queue](https://github.com/mattermost/platform/pulls) marked for the current release 
-  - (PM) Prioritize any developer documentation tickets
+3. PM:
-  - (PM) Draft [GitLab ticket](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/942) to take next Mattermost version in the Omnibus, but do not post until RC1 is cut
+  1. Review all [Severity 1 bugs (data loss or security)](https://mattermost.atlassian.net/secure/IssueNavigator.jspa?mode=hide&requestId=10600) to consider for adding to Hotfix list
-- (PM) Check testing is complete 
+  - Update documentation:
-  - (PM) Works with Ops to check the [Quality Gate](https://github.com/mattermost/process/blob/master/release/quality-gates.md) for feature complete
+    1. Make Changelog PR with updates for latest feature additions, known issues, and contributors
-  - (PM + Dev) Sign-off testing of their feature areas (i.e. PM/dev either signs-off that their area is well tested, or they flag that potential quality issues may exist)
+    - Make NOTICE.txt PR for any new libraries added from dev, if not added already 
-- **(Team) Feature Complete Meeting (10:15am PST)**
+    - Prioritize any developer documentation tickets
-  - (PM) Leads review of Changelog
+    - Draft [GitLab ticket](https://gitlab.com/gitlab-org/omnibus-gitlab/issues/942) to take next Mattermost version in the Omnibus, but do not post until RC1 is cut
-  - (Team) Each team member discusses worst bug (10-15s) 
+  - Coordinate testing:
-  - (PM) Review feature list for next release
+    1. Work with Ops to check the [Quality Gate](https://github.com/mattermost/process/blob/master/release/quality-gates.md) for feature complete
-  - (Marketing) Share draft of marketing announce for next release
+    - Receive testing sign-off from feature area owners (i.e. PM/Dev either signs-off that their area is well tested, or flags potential quality issues that may exist)
-- (Marketing) Communicates checklist of items needed by specific dates to write the blog post announce (e.g. screenshots, GIFs, 
+    - Check that Release Candidate Testing Spreadsheet is up to date
-- (Ops) Post Announce Date in Release channel + update the channel header to reflect date
+- **(Team) Feature Complete Meeting (10:15am PST)**:
-- (Ops) Mail out mugs to any new contributors
+  1. (PM) Leads review of Changelog
+  - (Team) Each team member discusses worst bug (10-15s) 
+  - (PM) Review feature list for next release
+  - **_(Marketing) Share draft of marketing announce for next release_**
+- Marketing:
+  1. Communicate checklist of items needed by specific dates to write the blog post announce (e.g. screenshots, GIFs, documentation) and begins to write the blog post, tweet, and email for the release announcement
  
  ### (T-minus 5 working days) Code Complete and Release Candidate Cut 
-- (Ops) Post this checklist in Release channel 
+
-- (Ops) For the next release, create team meetings on Feature Complete and Code Complete dates
+1. Ops:
-- (PM) Remove "Under Development" notice for current release from Changelog on master 
+  1. Post this checklist in Release channel 
+  - For the next release, create team meetings on Feature Complete and Code Complete dates
+- PM: 
+  1. Remove "Under Development" notice for current release from Changelog on master 
+  - Assign each area of the release testing spreadsheet to a team member
 - **(Team) Code Complete Meeting (10:15am PST meeting)** 
-  - (Ops) Walks through each item of this checklist
+  1. (Ops) Walk through each item of this checklist
-  - (PM) Assigns each area of the release testing spreadsheet to a team member
+  - (Dev) Last check of tickets that need to be merged before RC1
-  - (Dev) Last check of tickets that need to be merged before RC1
+  - (Team) Each team member discusses worst bug (10-15s) 
-  - (Team) Each team member discusses worst bug (10-15s) 
 - **Code Complete** is declared after meeting
-  - (Dev) Prioritize reviewing, updating, and merging of pull requests for current release until there are no more tickets in the [pull request queue](https://github.com/mattermost/platform/pulls) marked for the current release 
+- Dev:
-  - (Build) Master is tagged and branched and “Release Candidate 1″ is cut (e.g. 1.1.0-RC1) according to the [Release Candidate Checklist](https://github.com/mattermost/process/blob/master/release/create-release-candidate.md)
+  1. Prioritize reviewing, updating, and merging of pull requests for current release until there are no more tickets in the [pull request queue](https://github.com/mattermost/platform/pulls) marked for the current release 
-  - (PM) Create meta issue for regressions in GitHub (see [example](https://github.com/mattermost/platform/issues/574))
+- Build:
-  - (PM) Include link to meta-issue in release notes of RC1
+  1. Master is tagged and branched and “Release Candidate 1″ is cut (e.g. 1.1.0-RC1) according to the [Release Candidate Checklist](https://github.com/mattermost/process/blob/master/release/create-release-candidate.md)
-  - (PM) Tweet announcement that RC1 is ready (see [example](https://twitter.com/mattermosthq/status/664172166368264192))
+- PM:
-  - (PM) Submit GitLab ticket to take next Mattermost version in the Omnibus
+  1.  Create meta issue for regressions in GitHub (see [example](https://github.com/mattermost/platform/issues/574))
+  - Include link to meta-issue in release notes of RC1
+  - Submit GitLab ticket to take next Mattermost version in the Omnibus
+- Marketing:
+  1.  Tweet announcement that RC1 is ready (see [example](https://twitter.com/mattermosthq/status/664172166368264192))
  
  ### (T-minus 4 working days) Release Candidate Testing 
-- (Team) Final testing is conducted by the team on the acceptance server and any issues found are filed
+
-- (Build) Tests upgrade from previous version to current version, following the [Upgrade Guide](https://github.com/mattermost/platform/blob/master/doc/install/Upgrade-Guide.md) 
+1. Ops:
-  - Database upgrade should be tested on both MySQL and Postgres
+  1. Post this checklist in Release channel
- - (Ops) Posts copy of the **Release Candidate Testing** checklist into Town Square in PRODUCTION 
+  - Queue an agenda item for next team meeting for Release Process Kaizen/Q&A
-    - (Ops) Moves meeting, test and community channels over to the production version of RC, and posts in Town Square asking everyone to move communication over to the new team for testing purposes
+- Build:
-    - (PM) Test feature areas and post bugs to Bugs/Issues in PRODUCTION 
+  1. Test upgrade from previous version to current version, following the [Upgrade Guide](https://github.com/mattermost/platform/blob/master/doc/install/Upgrade-Guide.md) 
-    - (Ops) Runs through general testing checklist on RC1 and post bugs to Bugs/Issues in PRODUCTION 
+  - Database upgrade should be tested on both MySQL and Postgres
-   - (PM & DEV) Add **#p1** tag to any “Blocking” issue that looks like a hotfix to the RC is needed, and create a public ticket in Jira. Blocking issues are considered to be security issues, data loss issues, issues that break core functionality, or significantly impact aesthetics. 
+- Team:
-- (PM) Updates the GitHub meta issue
+  1. Test assigned areas of the Release Candidate Testing Spreadsheet and file any bugs found in Jira
-  - (PM) Posts links to all issues found in RC as comments on the meta issue
+  - Post a link to any "Blocking" issue that may need a hotfix to the RC in the Release room, with the **#p1** tag. Blocking issues are considered to be security issues, data loss issues, issues that break core functionality, or significantly impact aesthetics. 
-  - (PM) Updates description to include approved fixes
+- PM:
-  - (PM) Posts screenshot and link to final tickets for next RC to the Release room
+  1. Post links to all issues found in RC as comments on the meta issue
-  - (PM) Updates Release Notes with any new issues that will not be fixed for the current version
+  - Update the meta issue description to include approved fixes
-- (PM & DEV leads) Triage hotfix candidates and decide on whether and when to cut next RC or final
+  - Post screenshot and link to final tickets for next RC to the Release room
-- (Dev) PRs for hotfixes made to release branch, and changes from release branch are merged into master
+  - Update Changelog “Known Issues” section with any significant issues that were found and not fixed for the final release
- - (Ops) Tests approved fixes on master
+- Standup:
-  - (Dev) Pushes next RC to acceptance after testing is complete and approved fixes merged
+  1. **_Triage hotfix candidates and decide on whether and when to cut next RC or final_**
-- (Dev) pushes next RC to acceptance and announces in Town Square on PRODUCTION 
+  - **_If no blocking issues are found, PM, Dev and Ops signs off on the release_**
-  - (PM) closes the meta issue after the next RC is cut, and opens another ticket for new RC
+- Dev:
-- (Ops) verifies each of the issues in meta ticket is fixed
+  1. PRs for hotfixes made to release branch, and changes from release branch are merged into master
- - (PM) If no blocking issues are found, PM, Dev and Ops signs off on the release
+- Ops:
+  1. **_Tests approved fixes on master_**
+- Build: 
+  1. Push next RC to acceptance after testing is complete and approved fixes merged, announces in Town Square on pre-release.mattermost.com/core
+- PM:
+  1. Closes the meta issue after the next RC is cut, and opens another ticket for new RC
+- Ops:
+  1. Verifies each of the issues in meta ticket is fixed
  
  ### (T-minus 2 working days) Release Build Cut
-- (Ops) Post this checklist in Release channel 
+
-- (Build) Tags a new release (e.g. 1.1.0) and runs an official build which should be essentially identical to the last RC
+The final release is cut. If an urgent and important issue needs to be addressed between major releases, a bug fix release (e.g. 1.1.1) may be created
- - (PM) Any significant issues that were found and not fixed for the final release are noted in the release notes
+
-   - If an urgent and important issue needs to be addressed between major releases, a bug fix release (e.g. 1.1.1) may be created
+1. Ops:
-- (PM) Copy and paste the Release Notes from the Changelog to the Release Description
+  1. Post this checklist in Release channel 
-- (PM) Update the mattermost.org/download page
+- Build:
-- (PM) Update the AMI links on mattermost.org/installation
+  1. Tags a new release (e.g. 1.1.0) and runs an official build which should be essentially identical to the last RC
-- (PM) Close final GitHub RC meta ticket
+  - Delete RCs after final version is shipped
-- (Dev) Delete RCs after final version is shipped
+- PM:
-- (Marketing) Finalize marketing
+  1. Copy and paste the Release Notes from the Changelog to the Release Description
-  - (Marketing) Finalize mailchimp email blast
+  - Update the mattermost.org/download page
-  - (Marketing) Finalize blog post and put on timer for release
+  - Update the AMI links on mattermost.org/download and mattermost.org/installation
-  - (Marketing) Finalize tweet announcement
+  - Close final GitHub RC meta ticket
-  - (Marketing) Finalize announcement on general mailing list
+- Marketing:
-  - (Marketing) Finalize announcement for gitlab.mattermost.com
+  1. Finalize mailchimp email blast
+  - Finalize blog post and put on timer for release
+  - Finalize tweet announcement
+  - Finalize announcement on general mailing list
+  - Finalize announcement for gitlab.mattermost.com
 
 ### (T-minus 0 working days) Release Day
-- (Ops) Post this checklist in Release channel 
+
-- (PM) Confirm marketing has been posted (animated GIFs, screenshots, mail announcement, Tweets, blog posts) 
+1. Ops: 
-- (PM) Close the release in Jira
+  1. Post this checklist in Release channel 
-- (PM) Set header of next release as UNDER DEVELOPMENT in CHANGELOG on master
+  - Post key dates for the next release in the header of the Release channel
-- (Dev) Check if any libraries need to be updated for the next release, and if so bring up in weekly team meeting
+- PM:
-- (Ops) Post key dates for the next release in the header of the Release channel
+  1. Close the release in Jira
-- (Ops) Queue an agenda item for next team meeting for Release Process Kaizen/Q&A
+  - Set header of next release as UNDER DEVELOPMENT in CHANGELOG on master
+- Dev:
+  1. Check if any libraries need to be updated for the next release, and if so bring up in weekly team meeting
+- Marketing:
+  1. Confirm marketing has been posted (animated GIFs, screenshots, mail announcement, tweets, blog posts)