Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix ROOT version in docs #1043

Merged
merged 1 commit into from
Sep 24, 2024
Merged

Fix ROOT version in docs #1043

merged 1 commit into from
Sep 24, 2024

Conversation

HDembinski
Copy link
Member

We opt for a manual update strategy for the ROOT version, because it changes slowly and an efficient way to do it automatically in CI is elusive. Instructions were added to the release.md instructions and conf.py in the doc folder.

What is the problem with doing it in CI?

Since the ROOT repo is huge, we want to make shallow clones for git submodules, but then we cannot determine the relation of the commit to the closest tag, because that history which connects tag and commit is not there. Checking out all tags with git pull --tags takes a lot of bandwidth, and is not enough. We also need to check out the history between the latest tag and the commit. We don't know which tag the commit is closest to, so the best way would be to iteratively load the most recent history until the commit is connected to a tag.

@HDembinski HDembinski merged commit b18cee3 into develop Sep 24, 2024
9 checks passed
@HDembinski HDembinski deleted the root_version_fix branch September 24, 2024 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant