Skip to content

17.3 required upgrade stop planning

17.3 is an upgrade stop.

Creating this planning issue to collect list of changes require stop @ 17.3.

You can review the Common scenarios that require stops and avoiding required stops to confirm, if you are still not sure after reviewing the documentation, please leave a comment with the link to your issue/epic in this issue for others to review.

If your change requires stop and cannot wait till %17.3, please reach out to @dorrino and @plu8.

To help to determine whether %17.3 is a required stop, please try to list the issues below before 2024-08-02 (your local time).

List of changes require stop @ %17.3

Below is for the issue author only.

Notes for issue author

After the issue creation:

Message template: The Distribution::Deploy group created an issue (link to this issue) to determine if x.y needs to bea required upgrade stop. Please review your upcoming changes and share any may require upgrade stop on the issue (link to this issue), thank you.

  • Update "Next Required Stop" bookmark on the #g_distribution to this issue link
  • Update EWIR
  • Post to Slack channel #engineering-fyi and cross post to
    • #eng-managers
    • #cto

Once the decision made:

If x.y is an upgrade stop:

Message template: An update on the next upgrade stop (link to this issue), x.y is a planned upgrade stop. It is a great opportunity to plan tasks as mentioned on Adding required stops and Avoiding required stops.

  • Comment on this issue
  • Update EWIR
  • Post to Slack channel #engineering-fyi and cross post to
    • #eng-managers
    • #cto
    • #whats-happening-at-gitlab
    • #support_self-managed

If x.y is not an upgrade stop:

Message template: An update on the next upgrade stop (link to this issue), x.y is NOT a planned upgrade stop.

  • Comment on this issue
  • Update EWIR
  • Post to Slack channel #engineering-fyi and cross post to
    • #eng-managers
    • #cto

/cc @gitlab-org/development-leaders

Edited by Peter Lu