[Proposal] Delete unmaintained release branches #7614

New Issue

GiteaMirror · 2025-11-02T07:31:24-06:00

GiteaMirror commented

2025-11-02 07:31:24 -06:00

Originally created by @delvh on GitHub (Jul 22, 2021).

Currently, there are way too many branches: There is main, and then there is release/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.

Originally created by @delvh on GitHub (Jul 22, 2021). Currently, there are way too many branches: There is `main`, and then there is `release/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.

GiteaMirror commented

2025-11-02 07:31:25 -06:00

@zeripath commented on GitHub (Jul 22, 2021):

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.

@zeripath commented on GitHub (Jul 22, 2021): 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.

GiteaMirror commented

2025-11-02 07:31:25 -06:00

@zeripath commented on GitHub (Jul 22, 2021):

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

@zeripath commented on GitHub (Jul 22, 2021): 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

GiteaMirror commented

2025-11-02 07:31:25 -06:00

@yardenshoham commented on GitHub (Apr 29, 2023):

Let's do it

@yardenshoham commented on GitHub (Apr 29, 2023): Let's do it

GiteaMirror commented

2025-11-02 07:31:26 -06:00

@lunny commented on GitHub (Apr 30, 2023):

We can save the commit id in some code file and then delete these tags before 1.14.

@lunny commented on GitHub (Apr 30, 2023): We can save the commit id in some code file and then delete these tags before 1.14.

GiteaMirror commented

2025-11-02 07:31:26 -06:00

@delvh commented on GitHub (Apr 30, 2023):

Sidenote: At the time I opened this issue, 1.16 was the current main branch.
By now, it is basically 1.20.

@delvh commented on GitHub (Apr 30, 2023): Sidenote: At the time I opened this issue, 1.16 was the current main branch. By now, it is basically 1.20.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#7614