WIP: Dropping subgroup support on mysql
This blog post outlines the reasons why we are dropping subgroup support on MySQL. Please feel free to add any details on why we are dropping support and more information on the migration path.
Merge request reports
Activity
1 --- 2 title: "Dropping support for subgroups MySQL " 3 author: Mike Bartlett 4 author_gitlab: mydigitalself 5 author_twitter: mydigitalself 6 categories: GitLab 7 description: "Subgroups will no longer be available for GitLab instances on MySQL from GitLab 9.2" 8 --- 9 10 In 9.0 we released an enhancement to group management by [introducing subroups](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#subgroups-ce-ee). 11 Unfortuntaly for performance and consistency, we are having to drop this feature on GitLab instances running MySQL. Subgroups will no longer be availble on MySQL in added 2 commits
@stanhu @mydigitalself Yes, and we should also announce this in the release post itself.
@mydigitalself Anything blocking from announcing this soon?
What is the message we intend to send to customers on MySQL? It seems from the current wording that we imply it is a second-class citizen.
Should we be more clear here on our plans? For example, something like "we will continue to support MySQL" or some other forward looking statement?
Otherwise I am sure we will get a lot of questions on what this means to someone on MySQL, and whether this is the only issue or if they can expect to see increasing disparity in support going forward.
mentioned in issue gitlab-pivotal/p-gitlab-ee#38
cc @lbot, as you may get calls when we announce this
Thanks @joshlambert. I think the bigger thing we will get questions about will be "What's the plan for MySQL going forward?"
Having spoken with @JobV about this, the decision is not to publish a separate post on this, but rather to include it in the 9.3 release post.
I'm just about to push a change to include it right near the top of the post for visibility in https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/5804
