Add guidelines to release post handbook (upgrade and performance)
The problem
Every month we add the sections "upgrade barometer" and "performance improvements" to the release post. But it is unclear who owns these sections, so we need to run after people to gather this info. Therefore, we need to figure what's the best way to do it and document it as a new guideline in the release post handbook.
Suggested solution
Upgrade barometer
To be added by the release manager, or by backend team leads (Sean, Douwe, Stan, Marin). Should include the following info before the review starts (6th working day before the 22nd):
- How should the upgrade be done? Please detail.
- Do we expect downtime? If so, how long will it take? Please detail.
- Are there any special cases, something important to note? Please detail.
Performance Improvents
To be added by the blog post author, stating that we are constantly improving performance as a whole, and linking to merged merge requests of that release milestone labeled with "performance", both to CE and EE, for example:
- https://gitlab.com/gitlab-org/gitlab-ce/merge_requests?scope=all&utf8=%E2%9C%93&state=merged&milestone_title=9.4&label_name[]=performance
- https://gitlab.com/gitlab-org/gitlab-ee/merge_requests?scope=all&utf8=%E2%9C%93&state=merged&milestone_title=9.4&label_name[]=performance
This is also to be included before the review starts (6th working day before the 22nd):
cc/ @JobV @joshlambert @bikebilly @smcgivern feedback is much appreciated.