Release 8.10.5
- Picked into respective
stable
branches.Picked into Stable
8.10 merged merge requests:-
gitlab-org/gitlab-ce!5670 -
gitlab-org/gitlab-ce!5706 -
gitlab-org/gitlab-ce!5746 -
gitlab-org/gitlab-ce!5754 -
gitlab-org/gitlab-ee!637
-
-
Check ce/8-10-stable
CHANGELOG -
Check ee/8-10-stable-ee
CHANGELOG-EE -
Merge ce/8-10-stable
intoee/8-10-stable-ee
-
Check omnibus-gitlab/8-10-stable
CHANGELOG -
Check omnibus-gitlab/8-10-stable-ee
CHANGELOG -
While waiting for tests to be green, now is a good time to start on the blog post: gitlab-com/www-gitlab-com!2880 (merged) -
Ensure tests are green on CE -
Ensure tests are green on EE -
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.4-ee..8-10-stable-ee -- db/migrate
=>
diff --git a/db/migrate/20160804150737_add_timestamps_to_members_again.rb b/db/migrate/20160804150737_add_timestamps_to_members_again.rb new file mode 100644 index 0000000..6691ba5 --- /dev/null +++ b/db/migrate/20160804150737_add_timestamps_to_members_again.rb @@ -0,0 +1,21 @@ +# rubocop:disable all +# 20141121133009_add_timestamps_to_members.rb was meant to ensure that all +# rows in the members table had created_at and updated_at set, following an +# error in a previous migration. This failed to set all rows in at least one +# case: https://gitlab.com/gitlab-org/gitlab-ce/issues/20568 +# +# Why this happened is lost in the mists of time, so repeat the SQL query +# without speculation, just in case more than one person was affected. +class AddTimestampsToMembersAgain < ActiveRecord::Migration
- DOWNTIME = false
- def up
- execute "UPDATE members SET created_at = NOW() WHERE created_at IS NULL"
- execute "UPDATE members SET updated_at = NOW() WHERE updated_at IS NULL"
- end
- def down
-
- end
+end ```
-
Tag the 8.10.5
version using therelease
task:```sh bundle exec rake "release[8.10.5]" ```
-
Add patch notice to 8.10 Regressions: ``` `8.10.5` has been tagged, further fixes will go into `8.10.6` as necessary. ```
-
Check that EE packages are built, CE packages are built and appears on packages.gitlab.com
: EE / CE -
In #infrastructure
:``` I'm going to deploy `8.10.5` to staging ```
-
Deploy 8.10.5
to staging.gitlab.com -
In #infrastructure
:``` I'm going to deploy `8.10.5` to production ```
-
Deploy 8.10.5
to GitLab.com -
Check that the 8.10.5
version was automatically created on https://version.gitlab.com -
Deploy the blog post -
Tweet (prepare the Tweet text below or paste the tweet URL instead): ``` GitLab 8.10.5 has been released to address a few bugs & improve performance: https://about.gitlab.com/2016/08/10/gitlab-8-dot-10-dot-5-released/ ```
-
Add ce/v8.10.5
CHANGELOG items toce/master
CHANGELOG -
Add ee/v8.10.5-ee
CHANGELOG-EE items toee/master
CHANGELOG-EE -
Add omnibus-gitlab/v8.10.5+ee.0
CHANGELOG items toomnibus-gitlab/master
CHANGELOG -
Create the next patch issue (if needed) using the patch_issue
task (and put a reference to it below):```sh bundle exec rake "patch_issue[8.10.6]" ``` https://gitlab.com/gitlab-org/gitlab-ce/issues/20814
For references: