Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitaly.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarthik Nayak <knayak@gitlab.com>2023-06-01 17:58:46 +0300
committerKarthik Nayak <knayak@gitlab.com>2023-06-02 12:28:11 +0300
commit8fddea2543e8248785e4f9e709b59f85cb163767 (patch)
treed300d30868603b8eb5c53cfcc60cdcd2355e71b1
parentcfd146b4d96acd8f1cb5ca06694e8631dff51368 (diff)
template: Add template fot Git version upgrade
Add a new issue template for the Git version upgrade. This should help us streamline our Git updates more.
-rw-r--r--.gitlab/issue_templates/Git Version Upgrade.md30
1 files changed, 30 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/Git Version Upgrade.md b/.gitlab/issue_templates/Git Version Upgrade.md
new file mode 100644
index 000000000..1140ff80a
--- /dev/null
+++ b/.gitlab/issue_templates/Git Version Upgrade.md
@@ -0,0 +1,30 @@
+/title Rollout Git version vX.XX.X
+
+## Changelog
+
+<!--
+Add the changelog related to the new version and how this impacts us. It is especially important to highlight changes that increase the risk for this particular upgrade.
+Would be really nice to point out contributions made by the Gitaly team, if any.
+-->
+
+## Steps
+
+- [ ] Introduce the new Git version behind a feature flag ([Reference](https://gitlab.com/gitlab-org/gitaly/-/merge_requests/5587)).
+ - [ ] Introduce the new bundled Git version in the [Makefile](/Makefile).
+ - [ ] Introduce the new bundled Git execution environment in the [Git package](/internal/git/version.go) behind a feature flag.
+- [ ] Roll out the feature flag.
+ - [ ] Create an issue for the rollout of the feature flag ([Reference](https://gitlab.com/gitlab-org/gitaly/-/issues/5030)).
+ - [ ] Optional: Create a [change request](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#change-request-workflows) in case the new Git version contains changes that may cause issues.
+ - [ ] Roll out the feature flag.
+- [ ] Update the default Git version. This must happen after the default-disabled flag has been released to avoid issues with zero-downtime upgrades.
+ - [ ] Remove the feature flag.
+ - [ ] Remove the old bundled Git execution environment.
+ - [ ] Remove the old bundled Git version in the [Makefile](/Makefile).
+ - [ ] Update the default Git distribution by updating `GIT_VERSION` to the new Git version in the [Makefile](/Makefile).
+- [ ] Optional: Upgrade the minimum required Git version. This is only needed when we want to start using features that have been introduced with the new Git version.
+ - [ ] Update the minimum required Git version in the [Git package](/internal/git/version.go). ([Reference](https://gitlab.com/gitlab-org/gitaly/-/merge_requests/5705))
+ - [ ] Update the minimum required Git version in the [README.md](/README.md).
+ - [ ] Update the GitLab release notes to reflect the new minimum required Git version. ([Reference](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/107565).
+
+/label ~"Category:Gitaly" ~"group::gitaly" ~"group::gitaly::git" ~"section::enablement" ~"devops::systems" ~"type::maintenance" ~"maintenance::dependency"
+/label ~"workflow::ready for development"