From: Lynne <dev@lynne.ee>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] forgejo labels
Date: Wed, 30 Jul 2025 14:37:02 +0900
Message-ID: <c13eabdd-c680-476b-967f-7614bc0f926f@lynne.ee> (raw)
In-Reply-To: <9eb491a1-553b-432d-a17b-ae0970a54d66@rothenpieler.org>
On 29/07/2025 02:37, Timo Rothenpieler wrote:
> On 7/28/2025 7:24 PM, Michael Niedermayer wrote:
>> On Mon, Jul 28, 2025 at 06:15:53PM +0200, Timo Rothenpieler wrote:
>>> On 7/28/2025 4:40 PM, Diederick C. Niehorster wrote:
>>>> On Mon, Jul 28, 2025 at 4:21 PM Michael Niedermayer
>>>> <michael@niedermayer.cc> wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> regression: issue aaddresses a regression
>>>>> bug: something is not working
>>>>>
>>>>> This is inconsistent
>>>>> Label X cannot sometimes mean "X is removed" and "X is added"
>>>>>
>>>>> bug seems meaning that the PR adds a bug
>>>>> regression seems meaning that the PR removes a regression
>>>>>
>>>>> IMO this should be done consistently
>>>>> a PR can have bugs and it can fix bugs
>>>>> a PR can cause regressions and it can fix regressions
>>>>
>>>> so lets rename the labels to bug_fix, regression_fix and add has_bug
>>>> and has_regression. The former two colored green, the latter two
>>>> colored red.
>>
>> This sounds reasonable
>>
>>
>> [...]
>>
>>> So for an issue, the label would imply that it reports a bug or
>>> regression,
>>> and for a PR that it fixes it respectively.
>>>
>>
>>> Having two split labels for that seems a little unnecessary.
>>
>> I dont know, i have only used forgejo for a few days
>
> This is purely convention we want to use, there's no established
> standard for that. Practically every project does something slightly
> different.
>
>>>
>>> Or we could just not use the bug/regession label on PRs, cause they
>>> do seem
>>> kinda off there.
>>
>> thats reasonable too, but it probably should then also not be possible to
>> select them.
>
> That is not an option, Labels apply to all issues, including PRs.
> Probably a valid feature request to post.
Could you at least rename issue/bug and issue/regression to just bug and
regression?
A bug is an issue, and a regression is also an issue. Its very redundant.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-07-30 5:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 14:20 Michael Niedermayer
2025-07-28 14:40 ` Diederick C. Niehorster
2025-07-28 16:15 ` Timo Rothenpieler
2025-07-28 17:24 ` Michael Niedermayer
2025-07-28 17:37 ` Timo Rothenpieler
2025-07-30 5:37 ` Lynne [this message]
2025-07-29 21:04 ` Frank Plowman
2025-07-29 22:40 ` Michael Niedermayer
2025-07-29 23:18 ` Kieran Kunhya via ffmpeg-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c13eabdd-c680-476b-967f-7614bc0f926f@lynne.ee \
--to=dev@lynne.ee \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git