Release post - GitLab 12.0
Process improvements? Have suggestions for improving the release post process as we go? Please capture them in the retrospective issue!
Review Apps: https://release-12-0.about-src.gitlab.com/2019/06/22/gitlab-12-0-released/
Release post:
- Intro: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-12-0/source/posts/2019-06-22-gitlab-12-0-released.html.md
- Items: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-12-0/data/release_posts/2019_06_22_gitlab_12_0_released.yml
- Images: https://gitlab.com/gitlab-com/www-gitlab-com/tree/release-12-0/source/images/12_0
Related files:
- Features YAML link: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-12-0/data/features.yml
- Features YAML Images link: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-12-0/source/images/feature_page/screenshots
- Homepage card: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-12-0/source/includes/home/ten-oh-announcement.html.haml
- MVPs: https://gitlab.com/gitlab-com/www-gitlab-com/blob/release-12-0/data/mvps.yml
Handbook references:
- Blog handbook: https://about.gitlab.com/handbook/marketing/blog/
- Release post handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/
- Markdown guide: https://about.gitlab.com/handbook/product/technical-writing/markdown-guide/
People:
- Release Post Managers: https://about.gitlab.com/handbook/marketing/blog/release-posts/managers/
- Release Managers: https://about.gitlab.com/community/release-managers/
| Release post manager | Tech writer | Messaging | Social |
|---|---|---|---|
| @jeremy | @eread | @johnjeremiah | @evhoffmann |
General contributions
Due date: 2019-06-14 (6th working day before the 22nd)
All contributions added by team members, collaborators, and Product Managers (PMs).
Author's checklist
Due date: 2019-06-14 (6th working day before the 22nd)
The PM leading the post is responsible for adding and checking the following items: @jeremy
-
Label MR: ~"blog post" release release post ~P1 -
Assign the MR to yourself -
Add a release post retrospective issue (example) and provide a link to it at the top of this MR description with the text Process Improvements? Have suggstions for improving the release post process as we go? Capture them in the [Retrospective issue](). -
Check the reviewers on Slack and add their names (and your own) replacing each @mentionin the MR description checklists -
Add milestone -
Update the links and due dates in this MR description -
Make sure the blog post have all initial files, as well as this MR template contains the latest template -
Add authorship (author's data) -
Ask the messaging lead to add the introduction by the 6th working day before the 22nd -
Add MVP (MVP block) -
Add MVP to data/mvps.yml -
Make sure the PM for the MVP feature adds a corresponding feature block if applicable, linking from the MVP section -
Add cover image ( 12_0-cover-image.jpg) (compressed) -
Add social sharing image ( gitlab-12-0-released.png) (compressed) -
Make sure all feature descriptions are positive and cheerful -
Make sure all features listed in the direction page are included in the post -
Mention the Distribution PM asking them if there's any relevant info to be added to the upgrade warning section. If not, delete the upgradeblock in the relese post data file -
Mention managers to remind them to add their team performance improvements: @gitlab-com/backend-managers and @gitlab-org/frontend/frontend-managers -
Check with the Messaging Lead on what the top features should be. -
Check if deprecations are included -
Alert people one working day before each due date (post a comment to #release-post Slack channel) -
Make sure all images (png, jpg, and gifs) are smaller than 300 KB each -
Run the release post through an automated spell and grammar check -
Pull masterinto the release post branch and resolve any conflicts -
Perform the content review
Recurring blocks
Due date: 2019-06-14 (6th working day before the 22nd)
The following sections are always present, and managed by the PM or Eng lead owning the related area:
-
Mention the below individuals after feature freeze -
Add GitLab Runner improvements: @brendan -
Add Omnibus improvements: @ebrinkman -
Add Mattermost update to the Omnibus improvements section: @ebrinkman -
Add Performance improvements: @DouweM, @smcgivern, @ayufan
Feature blocks
Due date: 2019-06-14 (6th working day before the 22nd)
The Product Managers are responsible for adding their feature blocks to the release post by the due date for general contributions. PMs are also responsible for adding any notable Community Contributions.
PMs: please check your box only when all your features and deprecations were added with completion (documentation links, images, etc). Pls don't check if there are still things missing.
Note: be sure to reference your Direction items and Release features. All items which appear in our Upcoming Releases page should be included in the relevant release post.
-
Mention the below individuals after feature freeze -
Manage (@jeremy) -
Plan (@ebrinkman) -
Create:Source Code (@jramsay) -
Create:Knowledge (@phikai) -
Create:Editor (@phikai) -
Verify (@brendan) -
Package (@trizzi) -
Release (@cstasik) -
Secure (@NicoleSchwartz ) -
Configure (@danielgruesso) -
Monitor - APM (@kencjohnston) -
Monitor - Debug & Health (@sarahwaldner) -
Fulfillment (@tipyn) -
Distribution (@ebrinkman)
Tip: make your own checklist:
- Primary features
- Improvements (secondary features)
- Deprecations
- Documentation updated
- Documentation links added to the post
- Community contributions documented and added to the post
- Illustrations added to the post (compressed, max width = 1000 pixels)
- Update
features.yml(with accompanying screenshots)
Review
Ideally, complete the review until the 4th working day before the 22nd, so that the 3rd and the 2nd working day before the release could be left for fixes and small improvements.
Content review
Due date: 2019-06-17 (5th working day before the 22nd)
Performed by the author of the post: @jeremy
-
Label MR: ~"blog post" release review-in-progress -
Check all comments in the thread (make sure no contribution was left behind) -
Check Features' names -
Check Features' availability (Core, Starter, Premium, Ultimate badges) -
Reorder primary and secondary features according to their relevance to the user (most impactful features come first) -
Check Documentation links (all feature blocks contain documentation_link) -
Make sure documentation_linklinks to feature webpages when available -
Features were added to data/features.yml(with accompanying screenshots) -
Check all images size < 300KB (compress them all with TinyPNG or similar tool) -
Pull master, resolve any conflicts -
Make sure all discussions in the thread are resolved -
Mention @markpundsack, @kencjohnston, @jlenny, and @ebrinkman to remind them to review -
Assign the MR to the next reviewer (structural check) -
Lock features.ymlwith File Locking on the 21st
Structural check
Due date: 2019-06-19 (3rd working day before the 22nd)
The structural review is performed by a technical writer: @eread
-
Add the label review-structure -
Pull masterinto the release post branch and resolve any conflicts -
Check frontmatter (entries, syntax) -
Check image_titleandtwitter_image -
Check image shadow applied correctly in release post data. Look for image_noshadow: truewhen an image already has shadow -
Ensure videos and iframes are wrapped in <figure class="video_container">tags (for responsiveness) -
Ensure all text is consistently hard wrapped at a suitable column boundary -
Check headings are in sentence case -
Check feature and product names are in capital case -
Check if images are harmonic/consistent -
Check any .gitkeepfiles and delete them if any -
Add or check cover img reference (at the end of the post). Data in cover_imgin release post Yaml file -
Ensure content is balanced between the columns (both columns are even) -
Ensure links have meaningful text for SEO (e.g., "click here" is bad link text) -
Check for badges consistency (applied to all headings) -
Double check that all features are documented -
Check that all links to about.gitlab.com content are relative URLs -
Check the anchor links in the intro. All links in the release post markdown file should point to something in the release post Yaml file -
Remove any remaining instructions (comments) from the release post files -
Run a dead link checker, e.g., Check my Links and ping reporters directly on Slack asking them to fix broken links -
Update the release post templates and release post handbook with anything that comes up during the process -
Pull masterinto the release post branch and resolve any conflicts (again) -
Report any problems from structural check in the #release-postchannel by pinging the reporters directly for each problem. Do NOT ping@allor@channelnor leave a general message that no one will pay attention to. If possible, ensure any issues are tracked by open discussions in the merge request -
Post a comment in the #company-announcementschannel linking to the review app + merge request reminding the team to take a look at the release post and to report problems in#release-post. Template to use (replace links):Hey all! This month's release post is almost ready! Take a look at it and report any problems in #release-post. MR: https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/1234 Review app: https://release-12-0.about-src.gitlab.com/2019/06/22/gitlab-12-0-released/ -
Remove the label review-structure. -
Assign the MR to the next reviewer (Marketing).
Further reviews
Due date: 2019-06-20 (2nd working day before the 22nd)
-
Marketing review (PMMs - messaging lead): @johnjeremiah -
Write the introduction (by the 6th working day before the 22nd) -
Check/copyedit feature blocks -
Check/copyedit features.yml -
Check/copyedit homepage blurb -
Check/copyedit social sharing text -
Mention Mark P (@markpundsack) for final check -
Remove the label review-in-progress -
Assign the MR back to the author
-
On the 22nd
The author of the post is responsible for merging the MR and following up with possible adjustments/fixes: @jeremy.
At 12:00 UTC
-
Read the important notes below -
At ~12:30 UTC, ping the release managers on the #releasesSlack channel asking if everything is on schedule, and to coordinate timing with them:- If anything is wrong with the release, or if it's delayed, you must ping
the messaging lead on
#release-postso that they coordinate anything scheduled on their side (e.g., press releases, other posts, etc). - If everything is okay, the packages should be published at 13:30 UTC, and available publicly around 14:10 UTC.
- Ask the release managers to ping you when the packs are publicly available (and GitLab.com is up and running on the release version)
- If anything is wrong with the release, or if it's delayed, you must ping
the messaging lead on
-
Mention @sumenkovic to remind him to send the swag pack to the MVP -
Check if all the anchor links in the intro are working -
Check if there are no broken links in the review app (use a dead link checker, e.g., Check my Links) -
Pull masterand fix any conflicts -
Check if there isn't any alert on Slack's #release-postand#company-announcementschannels -
Check if there isn't any alert on this MR thread -
Check if the tweet copy is ready and someone is ready to share on social media
At 13:50 UTC
-
Check if there aren't any conflicts. If there are any, pull masteragain and fix them.
Once the release manager confirmed that the packages are publicly available:
-
Unlock features.ymljust before merging. -
Verify that the 11.0 to 12.0 YT video has been made public: "It's still unlisted on YT, so we need to be sure to make it public just before the post goes live." -
Merge the MR at 14:10-14:20 UTC. -
Wait for the pipeline. It should take ~40min to complete. -
Check the look on social media with Twitter Card Validator and Facebook Debugger. -
Check for broken links again once the post is live. -
Share on social media (or make sure someone else does) only when you're sure everything is okay. -
Share the links to the post and to the tweet on the #release-postsand#company-announcementson Slack.
@dsumenkovic [is helping with the tweet](https://gitlab.slack.com/archives/C3TRESYPJ/p1560896427173700?thread_ts=1560894427.167300&cid=C3TRESYPJ when we go live, @evhoffmann is on the LinkedIn and FB posts at 9a Pacific. Thank you both very much for the help.
Important notes
- The post is to be live on the 22nd at 15:00 UTC. It should be merged and as soon as GitLab.com is up and running on the new release version (or the latest RC that has the same features as the release), and once all packages are publicly available. Not before. Ideally, merge it around 14:20 UTC as the pipeline takes about 40 min to run.
- The usual release time is 15:00 UTC but it varies according to the deployment. If something comes up and delays the release, the release post will be delayed with the release.
- Coordinate the timing with the release managers. Ask them to keep you in the loop. Ideally, the packages should be published around 13:30-13:40, so they will be publicly available around 14:10 and you'll be able to merge the post at 14:20ish.
- Once the post is live, wait a few minutes to see if no one spot an error (usually posted in #company-announcements), then share on Twitter, Facebook, and LinkedIn, or make sure someone (Emily vH, JJ, Marcia) does. Coordinate the social sharing with them beforehand.
- Keep an eye on Slack and in the blog post comments for a few hours to make sure no one found anything that should be fixed.
Merge request reports
Activity
added ~134987 priority1 ~111841 release post labels
assigned to @jeremy
marked the checklist item Label MR: ~"blog post" release release post ~P1 as completed
Per !23024 (merged) I removed myself from the issue description – I can see some more tweaks are needed to the template so I will create an MR for that now.
Resolved by Jeremy Watson (ex-GitLab)~"Service:Gitaly" Performance improvements:
- Delta Islands will improve clone speeds as it will optimise delta chains so these chains are all objects in either
refs/heads/*orrefs/tags/*. This will create less CPU load on the server at the time of a clone and Git will be able to send a higher rate of the data straight from disk - Fix an N + 1 on the ListLastCommitForTree RPC: gitlab-org/gitaly!1253 (merged)
- Use a different, and faster regexp engine for search: gitlab-org/gitaly!1241 (merged)
/cc @jramsay
Edited by Zeger-Jan van de Weg- Delta Islands will improve clone speeds as it will optimise delta chains so these chains are all objects in either
- Last reply by Jeremy Watson (ex-GitLab)
Resolved by Jeremy Watson (ex-GitLab)Secure Performance improvements:
-
Get rid of dind for DAST: Since docker-in-docker is no more required, the
dastDocker image (3GB) will now be cached on runners. Note that the image is updated weekly, so the cache will be invalidated every Monday.
@twoodham Could you please update if https://gitlab.com/gitlab-org/gitlab-ee/issues/11693 and https://gitlab.com/gitlab-org/gitlab-ce/issues/60879 make it to %12.0?
-
Get rid of dind for DAST: Since docker-in-docker is no more required, the
- Last reply by Jeremy Watson (ex-GitLab)
mentioned in issue gitlab-org/gitlab-runner#4311 (closed)
Mattermost section:
### GitLab Mattermost 5.11 GitLab 12.0 includes [Mattermost 5.11](https://mattermost.com/blog/mattermost-5-11/), an [open source Slack-alternative](https://mattermost.com/) whose newest release includes a new remote CLI tool, plus much more. This version also includes [security updates](https://mattermost.com/security-updates/) and upgrade from earlier versions is recommended.GitLab Mattermost 5.11
GitLab 12.0 includes Mattermost 5.11, an open source Slack-alternative whose newest release includes a new remote CLI tool, plus much more.
This version also includes security updates and upgrade from earlier versions is recommended.
mentioned in issue gitlab-org/gitlab-runner#4333 (closed)
CC @rdickenson as technical writer shadow.
Resolved by Jeremy Watson (ex-GitLab)MVP nominations
- Last reply by Kai Armstrong
added 1 commit
- 855eea86 - Update release 12.0 with Package group features
added 1 commit
- b6655789 - Update data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 16fdf673 - Update data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 420c1b6d - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 38fdf960 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- b1f24d27 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- d5ce8371 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 554dd186 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 688b5d3b - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 2 commits
added 1 commit
- 7cb3a25a - Update data/release_posts/2019_06_22_gitlab_12_0_released.yml
marked the checklist item Verify (@brendan) as completed
added 1 commit
- b69c0647 - Fix issue with release post yml causing broken build
added 1 commit
- 6650d537 - Update data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- e6558246 - Update data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- fe598e4f - Update data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 9db21996 - Update data/release_posts/2019_06_22_gitlab_12_0_released.yml
changed milestone to %12.0
- Resolved by Jeremy Watson (ex-GitLab)
@ebrinkman, is there any relevant info to be added to the upgrade warning section? If not, would be grateful if you could delete the
upgradeblock.
- Last reply by Fabian Zimmer
added 1 commit
- b608b8a8 - Update data/release_posts/2019_06_22_gitlab_12_0_released.yml
marked the checklist item Fulfillment (@tipyn) as completed
mentioned in issue #4646 (closed)
marked the checklist item Add a release post retrospective issue (example) and provide a link to it at the top of this MR description with the text
Process Improvements? Have suggstions for improving the release post process as we go? Capture them in the [Retrospective issue]().as completed-
@johnjeremiah, thanks for the first draft on the intro section. A kind reminder that this is due by end of day tomorrow (6 working days before the 22nd, or June 14th).
marked the checklist item Mention the Distribution PM asking them as completed
marked the checklist item Add cover image (
image_title) (compressed) as completed-
@gitlab-com/backend-managers and @gitlab-org/frontend/frontend-managers, please include any relevant performance improvements here. Thanks to those above (@zj, @plafoucriere) who have already mentioned these
marked the checklist item Mention managers to remind them to add their team performance improvements: @gitlab-com/backend-managers and @gitlab-org/frontend/frontend-managers as completed
added 1 commit
- 03723e57 - Update data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 3c60215e - Revert "Update data/release_posts/2019_06_22_gitlab_12_0_released.yml"
added 1 commit
- 87529efe - Revert "Updated Feature Block to remove issue"
added 1 commit
- 40fb9fab - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- e646b410 - Update data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- b72438a8 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 710b6aa3 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 9a69f560 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 6b579791 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 7e32728d - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 14f2538c - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- e4e7a1b5 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 892a2ab3 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 8dd772da - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- dd218a67 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- cbfdb030 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- ea486a7f - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- ccd2eb8e - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- d5886e02 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 66c2644e - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 061f5c1d - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 0a00bbca - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- d9b56fb7 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 05f0107f - Added GitLab Geo requires Hashed Storage in GitLab 12.0
marked the checklist item Create (@jramsay) as completed
added 1 commit
- c08c2868 - Added an upgrade warning about Hashed storage by default
added 1 commit
- 7feb2681 - Added GitLab Geo requires PostgreSQL Foreign Data Wrapper in GitLab 12.0
marked the checklist item Add Performance improvements: @DouweM, @smcgivern, @ayufan, @yorickpeterse as completed
added 1 commit
- d92abaa7 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 7 commits
- ff4b98b7 - Adding Sync from Web IDE to CI Runner feature to the features.yml and 12.0 release post pages
- 71e4cf93 - Update to add the documentation link for the file sync
- e9ce6b59 - Merge branch 'release-12-0' into 'phikai-editor-knowledge-release'
- 5cd3395c - Updates to release post for new feature name
- 65622319 - Updates to descriptions on `features.yml` to match and name/title changes based on docs
- 06982d9d - Merge branch 'release-12-0' into 'phikai-editor-knowledge-release'
- 31de90ea - Merge branch 'phikai-editor-knowledge-release' into 'release-12-0'
Toggle commit listadded 1 commit
- 3a87f9bd - Added warning for automatically upgrading PG.
added 1 commit
- 9327812c - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 200fa3c0 - Rework a few descriptions to remove leading "add"-type words at beginning
added 1 commit
- a9e1a76d - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
marked the checklist item Create:Editor (@phikai) as completed
marked the checklist item Create:Knowledge (@phikai) as completed
added 1 commit
- 19ca2fe8 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 2 commits
marked the checklist item Add Omnibus improvements: @ebrinkman as completed
marked the checklist item Plan (@ebrinkman) as completed
marked the checklist item Distribution (@ebrinkman) as completed
- Resolved by Jeremy Watson (ex-GitLab)
@amy.blais What should we include for Mattermost?
- Last reply by Jeremy Watson (ex-GitLab)
mentioned in merge request !24465 (merged)
marked the checklist item Distribution (@ebrinkman) as incomplete
marked the checklist item Configure (@danielgruesso) as completed
marked the checklist item Add MVP (MVP block) as completed
added 2 commits
added 2 commits
marked the checklist item Add Mattermost update to the Omnibus improvements section: @ebrinkman as completed
- Resolved by Jeremy Watson (ex-GitLab)
@ebrinkman: I missed seeing https://gitlab.com/gitlab-org/gitlab-ee/issues/10795 in the release post, do you think we might be able to add that improvement in? Looks like a great addition.
- Last reply by Jeremy Watson (ex-GitLab)
- Resolved by Jeremy Watson (ex-GitLab)
@brendan: Would you be able to add any
gitlab-runnerimprovements to the post? gitlab-org/gitlab-runner#2980 (closed) looks like a nice one. - Last reply by Jeremy Watson (ex-GitLab)
-
@sarahwaldner @kencjohnston: Worth adding https://gitlab.com/gitlab-org/gitlab-ce/issues/59266 to the post?
marked the checklist item Make sure all features listed in the direction as completed
added 3240 commits
-
4bdd40f6...48092b03 - 3239 commits from branch
master - 2d2e7624 - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
-
4bdd40f6...48092b03 - 3239 commits from branch
marked the checklist item Manage (@jeremy) as completed
marked the checklist item Check with the Messaging Lead on what the top features should be. as completed
- Resolved by Jeremy Watson (ex-GitLab)
@johnjeremiah, I added merge trains to the intro and refactored the description and title to match since Security Approvals is unlikely to make it into 12.0.
- Last reply by Kai Armstrong
added 1 commit
- ecd349a6 - Update link to photo for the dependency proxy
marked the checklist item Add GitLab Runner improvements: @brendan as completed
added 1 commit
- 28f88726 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 78ee6a8c - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 4c307c35 - Minor adjustment to the doc link for File Syncing to Web Terminal now that it's final and deployed
Resolved by Jeremy Watson (ex-GitLab)In 12.0 we are backporting the EE schema to CE, as part of the single codebase effort. This means CE will include a variety of EE migrations. We also remove some old migrations. Because of this, users have to upgrade to the latest 11.11.x version before upgrading to 12.0. When upgrading to future versions, users must first upgrade to 12.0.0. Omnibus already enforces this, but source installations do not.
We should include a notice about this in the upgrade barometer, and maybe tweet about it to make it extra clear. We could use the following snippet:
In 12.0 we merged the database changes made by Enterprise Edition over the years into Community Edition. As part of this work we have also removed various old migrations. Users upgrading to their GitLab installation must first upgrade to the latest 11.11 patch release, then upgrade to 12.0.0. When upgrading to a future version such as 12.1.0, users must first upgrade to 12.0.0. Failing to do so may result in migrations not being applied, which could lead to application errors.
Omnibus installations already enforce upgrading to 12.0.0, but source installations will have to take care of this manually.
cc @marin
Edited by Yorick Peterse- Last reply by Jeremy Watson (ex-GitLab)
added 1 commit
- 1833522e - Changed so the upgrade warning uses only one block
mentioned in epic gitlab-com/marketing&230 (closed)
added review-in-progress label
marked the checklist item Secure (@NicoleSchwartz ) as completed
marked the checklist item Secure (@NicoleSchwartz ) as incomplete
added 1 commit
- fc57c4cb - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- e684eb8d - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 5d46baa1 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
marked the checklist item Release (@cstasik) as completed
added 1 commit
- c17e949f - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- ac97adfb - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 3d8ebf98 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- b19b0560 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
marked the checklist item Secure (@NicoleSchwartz ) as completed
added 1 commit
- 7bed99ed - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 4a067ff6 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- f604dae8 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- d432be2b - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- ba005b3a - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
marked the checklist item Label MR: ~"blog post" release review-in-progress as completed
added 1 commit
- b931d005 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 6933b9a8 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
marked the checklist item Check all images size < 300KB (compress them all with TinyPNG or similar tool) as completed
marked the checklist item Monitor - Debug & Health (@sarahwaldner) as completed
marked the checklist item Distribution (@ebrinkman) as completed
added 1 commit
- ae1431c9 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- bde449f3 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- c396a7d6 - Removed 2 features that did not make the release
added 163 commits
-
b22c4725...5a522ef7 - 162 commits from branch
master - 666b4dbf - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
-
b22c4725...5a522ef7 - 162 commits from branch
marked the checklist item Mention @markpundsack, @kencjohnston, @jlenny, and @ebrinkman to remind them to review as completed
marked the checklist item Perform the content review as completed
added 1 commit
- c2531f16 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
mentioned in merge request !24571 (closed)
marked the checklist item Monitor - APM (@kencjohnston) as completed
added 1 commit
- 2de6a074 - Updating intro section. Removing Merge Trains
- Resolved by Jason Yavorska
@brendan there are two direction items that I can't seem to find in the blog post. Maybe they are there under another name but can you double check?
Just as an FYI, I also added the label to a few issues you'd included here that didn't have it. They definitely were worth including.
Edited by Jason Yavorska - Last reply by Jason Yavorska
- Resolved by Corrina Stasik
@cstasik https://gitlab.com/gitlab-org/gitlab-ee/issues/11417 is closed and has the %12.0 milestone but I can't find it in the release post. Can you please double check?
- Last reply by Corrina Stasik
- Resolved by Jeremy Watson (ex-GitLab)
@cstasik as best I can tell, Merge Trains MVC made it even though the issue is still open (waiting for follow up from @dosuken123 to confirm.) We should confirm and re-add to the release post.
- Last reply by Corrina Stasik
- Resolved by Jeremy Watson (ex-GitLab)
@trizzi https://gitlab.com/gitlab-org/gitlab-ee/issues/7934 has a milestone of %12.0 but is not listed here. I think though that was actually delivered in %11.11?
- Last reply by Tim Rizzi
- Resolved by Jeremy Watson (ex-GitLab)
@trizzi did https://gitlab.com/gitlab-org/gitlab-ce/issues/58271 make it or not? It has the %12.0 milestone, but is not closed and not in the blog post. Maybe it just needs to be moved to %12.1 (or somewhere.)
- Last reply by Jeremy Watson (ex-GitLab)
added 2 commits
added 1 commit
- c8d6c3cd - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 2a5fac18 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 5fb6442c - Update blog post to include last minute feature
added 133 commits
-
506adb6a...05e1312f - 130 commits from branch
master - f1f45611 - Merge branches 'master' and 'release-12-0' of...
- e1fb0239 - Update link for OAuth to Grafana
- 6b3ddec0 - Merge branch 'release-12-0' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
Toggle commit list-
506adb6a...05e1312f - 130 commits from branch
added 1 commit
- 20570a9e - Updated stage from manage > growth now that there is a growth.svg icon (which...
added 1 commit
- a9af5c6a - Promoted ip address restrict and updated link
added 9 commits
-
30f98c68...c3be6751 - 8 commits from branch
master - ca5f94c3 - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
-
30f98c68...c3be6751 - 8 commits from branch
assigned to @eread
unassigned @jeremy
added review-structure label
marked the checklist item Add the label review-structure as completed
added 34 commits
-
085c714b...54b12254 - 33 commits from branch
master - 71352f41 - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
-
085c714b...54b12254 - 33 commits from branch
added 1 commit
- f02d629c - Improve structure of release post header, with slight edits
marked the checklist item Check frontmatter (entries, syntax) as completed
marked the checklist item Run a dead link checker, e.g., Check my Links and ping reporters directly on Slack asking them to fix broken links as completed
added 50 commits
-
3f27ca57...dc27c2a2 - 47 commits from branch
master - 23eb7696 - Further structural check changes
- 4b4551db - Merge branch 'release-12-0' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
- a14a2530 - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
Toggle commit list-
3f27ca57...dc27c2a2 - 47 commits from branch
marked the checklist item Ensure links have meaningful text for SEO (e.g., "click here" is bad link text) as completed
marked the checklist item Report any problems from structural check in the
#release-postchannel by pinging the reporters directly for each problem. Do NOT ping@allor@channelnor leave a general message that no one will pay attention to. If possible, ensure any issues are tracked by open discussions in the merge request as completedadded 1 commit
- 253f0546 - Fix typo in Runner version in a deprecation note
marked the checklist item Remove the label review-structure. as completed
added 7 commits
-
253f0546...9c8f0414 - 6 commits from branch
master - 63823d4d - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
-
253f0546...9c8f0414 - 6 commits from branch
removed review-structure label
assigned to @johnjeremiah
unassigned @eread
added 1 commit
- 59af7516 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- 377cbc23 - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
added 1 commit
- ae0f3a7b - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
- Resolved by Jeremy Watson (ex-GitLab)
@lyle asked in https://gitlab.slack.com/archives/C3TRESYPJ/p1560956640202900 to consider adding a deprecation notice on the scope of support. I added this here to the Extras section. If that doesn't work, I'll add it to the deprecation area.
This didn't seem like a perfect fit alongside other deprecations since you can't simply avoid it if you don't upgrade to 12.0. I'll resolve this discussion when I've found a home for this guidance.
- Last reply by Jeremy Watson (ex-GitLab)
added 166 commits
-
06758d79...53fae3f6 - 165 commits from branch
master - 90c92153 - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
-
06758d79...53fae3f6 - 165 commits from branch
added 6 commits
-
40ccd19f...f42a5557 - 4 commits from branch
master - 62551038 - Anchor for epic quick action docs
- f1083688 - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
-
40ccd19f...f42a5557 - 4 commits from branch
added 1 commit
- c94e753c - Apply suggestion to data/release_posts/2019_06_22_gitlab_12_0_released.yml
-
cc: @markpundsack and @sfwgitlab
removed review-in-progress label
assigned to @jeremy
marked the checklist item Mention Mark P (@markpundsack) for final check as completed
marked the checklist item Remove the label review-in-progress as completed
marked the checklist item Marketing review (PMMs - messaging lead): @johnjeremiah as completed
mentioned in merge request !24789 (merged)
@johnjeremiah a heads up that I have an MR out for review adding changes towards this MR regarding GitLab Insights GA in 12.0 !24789 (merged).
I didn't commit changes to this MR directly to separate out the context since the changes in this MR has already gone through a review cycle. Relevant PM leads are already involved for review. I would assume we should merge !24789 (merged) into this MR first before merging this MR to
master.added 1 commit
- 9abb6937 - Removed extras section and moved to deprecations
added 2 commits
@johnjeremiah As discussed, here's a link to the video that needs to be added to 12.0 release post.
Gentle Reminder: It's still unlisted on YT, so we need to be sure to make it public just before the post goes live. Please let me know if you have any questions or requests on this. Thanks!
added 1 commit
- 03550854 - Adding the 11.0 to 12.0 reflections video to the intro
-
@jeremy FYI. Just added the 12.0 reflections video to the intro.
unassigned @johnjeremiah
added 10 commits
- 361dd9d4 - Add Insights to features.yml after GA
- 975b90ee - Add a section in the release post
- 477771ce - Removed competitors
- 64c06f83 - Added insights png
- d9d574d3 - Added image_url
- ec4d5063 - Consolidate links to project/insights/
- 9390cfa7 - Merge branch 'release-12-0' of gitlab.com:gitlab-com/www-gitlab-com into gitlab-insights-12-0
- 0fcda7df - Merge branch 'release-12-0' of gitlab.com:gitlab-com/www-gitlab-com into gitlab-insights-12-0
- a0770d65 - Merge conflict resolution
- 2cac0170 - Merge branch 'gitlab-insights-12-0' into 'release-12-0'
Toggle commit listmarked the checklist item Lock
features.ymlwith File Locking on the 21st as completedadded 350 commits
-
93f0e2e9...ce064e56 - 349 commits from branch
master - c8d2c7eb - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
-
93f0e2e9...ce064e56 - 349 commits from branch
-
I've done another quick read-through and everything is looking good. Release is looking on-track for tomorrow. Here's to 12.0!
marked the checklist item Read the important notes below as completed
marked the checklist item Check if there are no broken links in the review app (use a dead link checker, e.g., Check my Links) as completed
added 104 commits
-
c8d2c7eb...52342f65 - 103 commits from branch
master - abae1ba0 - Merge branch 'master' of gitlab.com:gitlab-com/www-gitlab-com into release-12-0
-
c8d2c7eb...52342f65 - 103 commits from branch
marked the checklist item Unlock
features.ymljust before merging. as completedmarked the checklist item Check the look on social media with Twitter Card Validator and Facebook Debugger. as completed
-
The post is now live at https://about.gitlab.com/2019/06/22/gitlab-12-0-released/. My gratitude to you all for your contributions, care, and support in another great release post.
mentioned in issue gitlab-org/gitaly#1751
mentioned in epic gitlab-org&1577
mentioned in merge request !75878 (merged)
