Skip to content
Snippets Groups Projects

GitLab 9.3 release post

Merged Victor Wu requested to merge release-9-3 into master
All threads resolved!
1 file
+ 6
6
Compare changes
  • Side-by-side
  • Inline
@@ -445,12 +445,12 @@ barometer:
# DEPRECATIONS
deprecations:
- feature_name: Dropping support for subgroups in MySQL
due: June 22nd 2017
- feature_name: Dropping Support for Subgroups in MySQL
due: June 22nd, 2017.
description: |
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).
Unfortunately for performance and consistency, we have to drop this
[introducing subroups](/2017/03/22/gitlab-9-0-released/#subgroups-ce-ee).
Unfortunately, for performance and consistency, we have to drop this
feature on GitLab instances running MySQL. Subgroups will no longer be
available on MySQL in GitLab 9.3 and the upgrade process will migrate any
subgroups to the root of the GitLab server.
@@ -458,12 +458,12 @@ deprecations:
While investigating some occurrences of inconsistencies with project
membership, we [discovered](https://gitlab.com/gitlab-org/gitlab-ce/issues/30472#note_27747600)
that our approach to implementing subgroups was
not efficient. While PostgreSQL provides easy workarounds, MySQL
not efficient enough. While PostgreSQL provides easy workarounds, MySQL
unfortunately did not provide any alternatives that did not require vastly
changing the way we store the hierarchy of groups.
In order to quickly address the issue, we have removed support from
subgroups in 9.3.
Subgroups in 9.3.
If you are running on MySQL and have created subgroups in your GitLab
instance, the upgrade process will convert any subgroups to regular groups.
Loading