From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] forgejo labels
Date: Mon, 28 Jul 2025 18:15:53 +0200
Message-ID: <8f57446e-9eb9-4b61-8851-1d51c5fe7dab@rothenpieler.org> (raw)
In-Reply-To: <CABcAi1jH3E50nZN9JiD1g9GEZZpLuHuGSY_TXgYAPTiDhrLqUA@mail.gmail.com>
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.
>
> Issues also need labels, and there "bug" and "regression" are fine,
> indicating that an issue flags a bug instead of, e.g., a feature
> request (and applying bug+regression makes sense).
Every PR is also an issue, labels apply to both.
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.
Or we could just not use the bug/regession label on PRs, cause they do
seem kinda off there.
_______________________________________________
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-28 16:16 UTC|newest]
Thread overview: 6+ 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 [this message]
2025-07-28 17:24 ` Michael Niedermayer
2025-07-28 17:37 ` Timo Rothenpieler
2025-07-29 21:04 ` Frank Plowman
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=8f57446e-9eb9-4b61-8851-1d51c5fe7dab@rothenpieler.org \
--to=timo@rothenpieler.org \
--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