Release 10.0.3

Create preparation MRs by following the instructions in release-tools.
- https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14568
- https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3032
- https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14590
- https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3039
Cherry-pick changes into preparation MRs following their instructions
Cherry-pick remaining merge requests labeled Pick into Stable for the current milestone using the Pick into Stable 10.0 merged merge requests page
Check for merge requests marked Pick into Backports and cherry-pick those which should go into this release.
Check the following list of critical issues/MRs which are to be included in 10.0.3. Where appropriate, ensure each has made it into both CE and EE
- !14613 (merged)
Merge CE 10-0-stable into EE 10-0-stable-ee following the [Merging a CE stable branch into its EE counterpart] guide
Sync stable branches: CE, EE, and Omnibus to dev, CE and Omnibus to github
Sync master branches to dev and github, as the CHANGELOG will be automatically updated on master during tagging
If needed, sync tags for dependencies (gitlab-shell, gitlab-workhorse, gitlab-pages, gitaly) to dev and github (when applicable)
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v10.0.2-ee..10-0-stable-ee -- db/migrate db/post_migrate =>
Check omnibus-gitlab/10-0-stable CHANGELOG.md
Check omnibus-gitlab/10-0-stable-ee CHANGELOG.md
While waiting for tests to be green, now is a good time to start on the blog post: BLOG_POST_MR
Ensure builds are green on CE stable branch and EE stable branch
Ensure builds are green on Omnibus CE stable branch and Omnibus EE stable branch
In #releases: I'm going to tag 10.0.3

Tag the 10.0.3 version using the release task:

```sh
# In the release-tools project:
bundle exec rake "release[10.0.3]"
```

Check progress of EE packages build and CE packages build
In #production: I'm going to deploy 10.0.3 to staging
On video call, deploy release 10.0.3 to staging.gitlab.com sh # In the takeoff project: bundle exec rake "deploy[staging, 10.0.3-ee.0]"
In #production: I'm going to deploy 10.0.3 to canary
On video call, deploy release 10.0.3 to canary.gitlab.com sh # In the takeoff project: bundle exec rake "deploy[canary, 10.0.3-ee.0]"
In #production: I'm going to deploy 10.0.3 to production
Make sure to announce the deploy on Twitter and GitLab.com
- With downtime: 1 hour before
- Without downtime: 15 minutes before
On video call, deploy release 10.0.3 to GitLab.com sh # In the takeoff project: bundle exec rake "deploy[production, 10.0.3-ee.0]"
From the build pipeline, manually publish public packages
Verify that packages appear on packages.gitlab.com: EE / CE
Verify that Docker images appear on hub.docker.com: EE / CE
Create the 10.0.3 version on https://version.gitlab.com
Deploy the blog post

Tweet (prepare the Tweet text below or paste the tweet URL instead):

```
GitLab 10.0.3 is released! BLOG_POST_URL DESCRIPTION OF THE CHANGES
```

In the 10.0 Regressions issue:
- Add the following notice:
```
`10.0.3` has been tagged, further fixes will go into `10.0.4` as necessary.
```
- Remove notes for the regressions fixed by version 10.0.3
Add omnibus-gitlab/10.0.3+ce.0 CHANGELOG.md items to omnibus-gitlab/master CHANGELOG.md

For references:

Edited Oct 09, 2017 by Robert Speicher