Skip to content

Rollout Git version v2.47.0

Changelog

https://gitlab.com/gl-gitaly/blogposts/-/merge_requests/4/

Steps

Introducing a new Git version

  • Add the new bundled Git version in the Makefile (Reference).
    • Update the build-bundled-git and install-bundled-git targets as necessary.
    • For a minor version bumps and above, add a new target under the # These targets build specific releases of Git. section corresponding to the new version.
  • Introduce the new bundled Git execution environment in the Git package behind a feature flag.
    • Create an issue for the rollout of the feature flag (Reference).
    • Optional: Create a change request in case the new Git version contains changes that may cause issues.
    • Roll out the feature flag.
    • Once the upgrade is deemed stable, remove the feature flag. You can do this in any release, including the release that adds the feature flag.

Removing an old Git version

  • Remove the old bundled Git version from the Makefile
    • Update the build-bundled-git and install-bundled-git targets as necessary.
    • Remove any unused targets under the # These targets build specific releases of Git. section corresponding to the old version.
  • Remove the old bundled Git execution environment from the Git package.

Upgrading the minimum required Git version

Optional: 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. (Reference)
  • Update the minimum required Git version in the README.md.
  • Update the GitLab release notes to reflect the new minimum required Git version. (Reference.
Edited by Karthik Nayak
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information