New features window is closed - things not merged into master up to
this day, will be released with next release.

7 working days before 22th (2019-07-11)

prepare GitLab Runner entries for the release blog post. Items can be generated with ./scripts/changelog2releasepost | less (executed in Runner's local working copy directory)

add release entry:

Add description to the SECONDARY FEATURES list using following template:

- name: GitLab Runner 12.1 available_in: [core, starter, premium, ultimate] documentation_link: 'https://docs.gitlab.com/runner' documentation_text: "Read through the documentation of GitLab Runner" description: | We're also releasing GitLab Runner 12.1 today! GitLab Runner is the open source project that is used to run your CI/CD jobs and send the results back to GitLab. ##### Most interesting changes: * [__Title__](https://gitlab.com/gitlab-org/gitlab-runner/merge_requests/__ID__) List of all changes can be found in GitLab Runner's [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-runner/blob/v12.1.0/CHANGELOG.md).

Pick into stable branch for RC2 phase

At this moment, until the next RC creation, we're in the pick into stable phase. The release manager should periodically
review the list of merged MRs with a pick into X.Y label:

checkout to master and merge 12-1-stable into master (only this one time, to update CHANGELOG.md and make the tag available for ./scripts/prepare-changelog-entries.rb in next stable release), push master:

checkout to master and merge 0-7-0-stable into master (only this one time, to update CHANGELOG.md and make the tag available for ./scripts/prepare-changelog-entries.rb in next stable release), push master:

Please check what deadline is set for General Contributions section in the release blog post
Merge Request. It should be 6th working day before the 22nd. In that case we can set our
deadline for 7th working day before 22nd, however if the deadline from the MR is earlier, then
use the earliest one.