-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
[Proposal] Delete unmaintained release branches #16512
Comments
Iirc there are unreleased commits on some of those branches but I guess we could just tag as eg v1.8.x-unreleased and then delete the branch. |
We also deleted a lot of old branches in the last release phase ... Prior to 1.14 we still had all of the branches up to 1.7 |
Let's do it |
We can save the commit id in some code file and then delete these tags before 1.14. |
Sidenote: At the time I opened this issue, 1.16 was the current main branch. |
Currently, there are way too many branches: There is
main
, and then there isrelease/v1.[8-15]
.As far as I know, the latest still maintained branch is
release/v1.14
.So, is there any reason to keep any release branch below
release/v1.14
?Because as far as I can see, the only thing the current branching pattern achieves is making a branch switch more complicated/ time consuming.
Alternatively, it would also be possible to open a fork that simply keeps the release branches that are currently unmaintained, if these branches are still wanted, although I doubt that.
The text was updated successfully, but these errors were encountered: