Skip to content

Track breaking changes that need to land in 13.0

NOTE - 13.0 IS SCHEDULED FOR MAY 22 AT THIS TIME (NO CHANGES)

Presently GitLab is planning to release our next major release on May 22nd: https://docs.gitlab.com/ee/policy/maintenance.html#versioning

Given the evolving situation due to COVID-19, employees are experiencing interruptions to their normal work day and environment. This includes school closures, restrictions on travel, oversaturated internet connections, and more.

These interruptions could have an impact on our delivery of key changes that are required to land in a major release. If some of these are delayed past May, the current major release timeframe, we may want to consider pushing to June so that we do not have to wait another year. Having this list will help us make that decision.

Changes which require a major release

  • Must Have: Yes if the change is required for %13.0 due to the impact of waiting another year
  • On Track: if progress is going well, if at risk, if it will not make it without a delay.

It would be great if we could update the items in the list by Monday of next week so we can get a sense of where we stand.

We should track the changes which require a major version change, to allow us to better understand whether we should delay %13.0.

Enablement

Currently devopsenablement is on track with breaking changes that require %13.0.

Change (Issue/Epic) Must Have? On Track?
PG11 and removal of 9.6 & 10 (gitlab-org&2414 (closed)) Yes
Puma opt-out (gitlab-org&954 (closed)) Yes
Remove node['gitlab'] monitoring deprecation in next major release(gitlab-org/omnibus-gitlab#4687 (closed)) No
Remove protected paths throttle from Omnibus (gitlab-org/omnibus-gitlab#4750 (closed)) No
Remove support for and references to postgresql['data_dir'] (gitlab-org/omnibus-gitlab#4806 (closed)) No
Remove Grafana reset logic during upgrade in GitLab 13.0 (gitlab-org/omnibus-gitlab#4891 (closed)) No
Rename Redis slave to replica (gitlab-org/omnibus-gitlab#5141 (closed)) No

Secure & Defend

Currently devopssecure is on track with breaking changes that require %13.0.

Change (Issue/Epic) Must Have? On Track?
Remove Docker in Docker requirement: gitlab-org/gitlab#37278 (closed) - Dep Notice Strong Desire
Drop support for license_management CI job, artifact and template License-Management.gitlab-ci.yml: gitlab-org/gitlab#8912 (closed) ?
Transition to rules syntax for Secure's vendored templates: gitlab-org&2300 (closed) Yes
Remove deprecated variable PIP_DEPENDENCY_PATH in gemnasium-python: gitlab-org/gitlab#13305 (closed) ?
Remove deprecated proprietary report format (clair scanner) for Container Scanning: gitlab-org/gitlab#35442 (closed) ?
Remove the legacy way of using DAST: gitlab-org/gitlab#31866 (closed) ?
Remove undefined value from Severity and Confidence: gitlab-org/gitlab#202685 (closed) ?
Drop usage of x-y-stable docker images and replace with pining to Major version: gitlab-org/gitlab#207128 (closed) - Dep Notice Strong Desire
Remove the legacy cve property from the JSON report: gitlab-org&2791 Strong Desire

Summarized list of Runner deprecation issues for 13.0

Change (Issue/Epic) Must Have? On Track?
Remove backported os.Expand() implementation Yes Yes
Remove support for array of strings when defining services for Docker Executor Yes Yes
Remove windows Batch from shell executor Yes Yes
Remove /debug/jobs/list?v=1 endpoint Yes Yes
Remove support for --docker-services flag on register command Yes Yes
Remove FF_USE_LEGACY_VOLUMES_MOUNTING_ORDER feature flag Yes Yes
Remove legacy build directory caching Yes Yes
Remove Windows 1803 support Yes Yes
Remove fedora/29 packages Yes Yes

Create:Editor

Change (Issue/Epic) Must Have? On Track?
Remove Snippet Content from search (UI and API breaking change) Yes

Release:Progressive Delivery

Change (Issue/Epic) Must Have? On Track?
Deprecate Feature Flag V1 API and UI Yes

Release:Release Management

Change (Issue/Epic) Must Have? On Track?
Deprecate Pages Legacy Architecture Yes
Deprecate old Release Evidence Yes

Configure:Configure

Change (Issue/Epic) Must Have? On Track?
Default Auto DevOps Postgres install to V2 Yes
Auto DevOps test job fails, breaken by only/except vs rules Yes
Change k8s api endpoints from deprecated beta to apps/v1 Yes

Verify:Continuous Integration

Change (Issue/Epic) Must Have? On Track?
Remove JenkinsDeprecatedService Yes

Manage: Access

Change (Issue/Epic) Must Have? On Track?
Projects API: Remove marked_for_deletion_on Yes
Groups API: Deprecate projects and shared_projects Yes
Edited by Taylor McCaslin