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

Repository layout: adopt a standard main branch will all the supported versions #109

Open
2 of 4 tasks
jouvin opened this issue Nov 16, 2024 · 0 comments
Open
2 of 4 tasks
Milestone

Comments

@jouvin
Copy link
Contributor

jouvin commented Nov 16, 2024

For reasons I forgot, when we created this repo at SVN -> Git migration time, we opted for a branch per OpenStack version and no master branch. It turned out not to be a great idea: it makes everything more complicated, including:

  • A release must tag several branches
  • Fixing a problem affecting several middleware versions requires several PRs
  • get-template-library must do complicated things to select all the branches to checkout
  • Obsoleting a branch requires renaming it with a .obsolete suffix rather than removing the corresponding set of templates in the master branch

My proposal is to move to a standard structure with a master branch and have a first level directory representing the OS version the templates must be used for, e.g. el7x-x86_64, el8x-x86_64, el8x-aarch64...

Addressing this issue requires:

  • Renaming the most recent branch to main
  • Import the other active branches, preserving their history. https://github.com/hraban/tomono may be a useful tool for achieving this.
  • Adapt release tools to the new (simpler) layout
  • Update the repository structure description in get-library-template
@jouvin jouvin added this to the 25.next milestone Nov 16, 2024
@jrha jrha changed the title Repository layout: adopt a standard master branch will all the supported versions Repository layout: adopt a standard main branch will all the supported versions Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant