Add latest changes from gitlab-org/gitlab@15-8-stable-ee

2 files changed, 85 insertions, 0 deletions

diff --git a/data/deprecations/15-8-deprecate-backups-support-for-openstack-rackspace-apis.yml b/data/deprecations/15-8-deprecate-backups-support-for-openstack-rackspace-apis.yml
new file mode 100644
index 00000000000..0097f59d1f9
--- /dev/null
+++ b/data/deprecations/15-8-deprecate-backups-support-for-openstack-rackspace-apis.yml
@@ -0,0 +1,13 @@
+- title: "Automatic backup upload using Openstack Swift and Rackspace APIs"  # (required) The name of the feature to be deprecated
+  announcement_milestone: "15.8"  # (required) The milestone when this feature was first announced as deprecated.
+  removal_milestone: "15.10"  # (required) The milestone when this feature is planned to be removed
+  end_of_support_milestone: "15.10"  # (optional) Use "XX.YY" format. The milestone when support for this feature will end.
+  breaking_change: true  # (required) If this deprecation is a breaking change, set this value to true
+  reporter: sranasinghe  # (required) GitLab username of the person reporting the deprecation
+  stage: Enablement  # (required) String value of the stage that the feature was created in. e.g., Growth
+  issue_url: https://gitlab.com/gitlab-org/gitlab/-/issues/387976  # (required) Link to the deprecation issue in GitLab
+  body: |  # (required) Do not modify this line, instead modify the lines below.
+    We are deprecating support for [uploading backups to remote storage](https://docs.gitlab.com/ee/raketasks/backup_gitlab.html#upload-backups-to-a-remote-cloud-storage) using Openstack Swift and Rackspace APIs. The support for these APIs depends on third-party libraries that are no longer actively maintained and have not been updated for  Ruby 3. GitLab is switching over to Ruby 3 prior to EOL of Ruby 2 in order to stay up to date on security patches.
+
+    - If you're using OpenStack, you need to change you configuration to use the S3 API instead of Swift.
+    - If you're using Rackspace storage, you need to switch to a different provider or manually upload the backup file after the backup task is complete.
diff --git a/data/whats_new/20230220001_15_08.yml b/data/whats_new/20230220001_15_08.yml
new file mode 100644
index 00000000000..30f1f1ea8d7
--- /dev/null
+++ b/data/whats_new/20230220001_15_08.yml
@@ -0,0 +1,72 @@
+- name: Block merges unless external status checks pass
+  description: |  # Do not modify this line, instead modify the lines below.
+    You can now configure projects to block merge request merges unless all external status checks pass. This allows you to confidently rely on external systems as part of your GitLab workflows and ensure that all required steps are completed before the code is merged.
+
+    When configured, users can only merge merge requests if external status checks pass and the green checkmark is displayed on the merge request. If an external status check is pending or failed, merging the merge request is blocked.
+
+  stage: govern
+  self-managed: true
+  gitlab-com: true
+  available_in: [Ultimate]
+  documentation_link: https://docs.gitlab.com/ee/user/project/merge_requests/status_checks.html#block-merges-of-merge-requests-unless-all-status-checks-have-passed
+  image_url: https://about.gitlab.com/images/15_8/manage-block-external-status-checks.png
+  published_at: 2023-01-22
+  release: 15.8
+- name: SCIM support for self-managed GitLab
+  description: |  # Do not modify this line, instead modify the lines below.
+    Self-managed GitLab now supports the open standard System for Cross-domain Identity Management (SCIM), which allows you to automatically:
+
+        - Create users.
+        - Remove users by deactivating their SCIM identities.
+
+      Previously, this was only available for GitLab.com. SCIM enables GitLab administrators to completely automate their user lifecycle management.
+  stage: manage
+  self-managed: true
+  gitlab-com: false
+  available_in: [Premium, Ultimate]
+  documentation_link: https://docs.gitlab.com/ee/user/admin_area/settings/scim_setup.html
+  image_url: https://about.gitlab.com/images/15_8/manage-scim-token.png
+  published_at: 2023-01-22
+  release: 15.8
+- name: Migrate projects when migrating groups using direct transfer
+  description: |  # Do not modify this line, instead modify the lines below.
+      We are excited to announce the availability of migrating GitLab projects by direct transfer Beta. Now, you can migrate group and project resources together when using direct transfer. You can use direct transfers to migrate between GitLab instances or
+      within the same GitLab instance.
+
+      Migrating projects when [migrating groups using direct transfer](https://docs.gitlab.com/ee/user/group/import/#migrate-groups-by-direct-transfer-recommended) is a major
+      improvement from migrating groups and projects using [file exports](https://docs.gitlab.com/ee/user/project/settings/import_export.html) because:
+
+      - You don't need to manually export each project to a file and then import all those export files to a new location. Now all projects
+        within a top-level group are migrated automatically, making your work more efficient.
+      - When migrating from self-managed GitLab to GitLab.com, user associations (such as comment author) are not changed to the user who is importing the
+        projects. Migration using direct transfer maps users and their contributions correctly, provided
+        [a few conditions are met](https://docs.gitlab.com/ee/user/group/import/#preparation).
+
+      This feature is available on GitLab.com. You can migrate from a self-managed GitLab to GitLab.com
+      right now!
+
+      To enable it on GitLab self-managed instances, see the linked documentation.
+
+      Learn more about migrating GitLab projects by direct transfer Beta and what’s coming next in our recent [blog post](https://about.gitlab.com/blog/2023/01/18/try-out-new-way-to-migrate-projects/).
+  stage: manage
+  self-managed: false
+  gitlab-com: true
+  available_in: [Free, Premium, Ultimate]
+  documentation_link: https://docs.gitlab.com/ee/user/group/import/#migrate-groups-by-direct-transfer-recommended
+  image_url: https://about.gitlab.com/images/15_8/groups-import-with-projects.png
+  published_at: 2023-01-22
+  release: 15.8
+- name: View estimated queuing time for runners in the Admin Area
+  description: |  # Do not modify this line, instead modify the lines below.
+        A key input in GitLab Runner fleet optimization is having deep insights into queue performance over time. While today there are historical queue duration metrics available for each job on a runner in the Admin Area view, there is no simple mechanism to determine the current queue performance for runners.
+
+        With the new estimated queue time feature, you are now able to, at a glance, determine the median estimated wait time for all instance runners. This data will enable you to proactively identify potential CI job execution issues for your organization's developers and provide insights to inform decisions on configuration or resource changes to optimize your runner fleet.
+
+  stage: verify
+  self-managed: true
+  gitlab-com: false
+  available_in: [Ultimate]
+  documentation_link: https://docs.gitlab.com/ee/ci/runners/configure_runners.html#view-statistics-for-runner-performance
+  image_url: https://about.gitlab.com/images/15_8/admin-runners-estimated-queue-wait-time.png
+  published_at: 2023-01-22
+  release: 15.8