Proposal: Custom release status or release labels #3741

New Issue

GiteaMirror · 2025-11-02T05:23:52-06:00

GiteaMirror commented

2025-11-02 05:23:52 -06:00

Originally created by @davidsvantesson on GitHub (Aug 6, 2019).

Currently a release can have three different statuses: Draft, Pre-Release and Stable. From what I understand only Draft has a specific meaning (allowing to save before tag is created). To allow different use cases it would be nice if custom release statuses would be supported. For example someone might want to mark a release as 'Production', 'Obsolete' etc.

Maybe it can be something similar as Issue Labels with predefined label sets and possibility to add new release labels for a specific repo. That would allow to have multiple labels on same release. Also future functionality could add possibility to filter releases on label.

Originally created by @davidsvantesson on GitHub (Aug 6, 2019). Currently a release can have three different statuses: Draft, Pre-Release and Stable. From what I understand only Draft has a specific meaning (allowing to save before tag is created). To allow different use cases it would be nice if custom release statuses would be supported. For example someone might want to mark a release as 'Production', 'Obsolete' etc. Maybe it can be something similar as Issue Labels with predefined label sets and possibility to add new release labels for a specific repo. That would allow to have multiple labels on same release. Also future functionality could add possibility to filter releases on label.

GiteaMirror added the type/proposal label 2025-11-02 05:23:52 -06:00

GiteaMirror commented

2025-11-02 05:23:53 -06:00

@kdumontnu commented on GitHub (Feb 7, 2024):

I agree a lot with this.

We've had a lot of users (that don't have github experience) asking what the difference between Pre-Release and Stable is. It's odd that we prescribe a very specific notation here when we have set the precedence for labels elsewhere (in repo topics, issues, etc.).

Many users have specific lifecycle statuses for projects they would like to use (eg. QA Validated, Obsolete, etc).

@kdumontnu commented on GitHub (Feb 7, 2024): I agree a lot with this. We've had a lot of users (that don't have github experience) asking what the difference between `Pre-Release` and `Stable` is. It's odd that we prescribe a very specific notation here when we have set the precedence for labels elsewhere (in repo topics, issues, etc.). Many users have specific lifecycle statuses for projects they would like to use (eg. `QA Validated`, `Obsolete`, etc).

GiteaMirror referenced this issue

2025-11-02 12:25:38 -06:00

[PR #3760] [MERGED] Sample config: update LOCAL_ROOT_URL description for PROTOCOL = 'unix' case #17072

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#3741