From: Pierre-Anthony Lemieux via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>,
Pierre-Anthony Lemieux <pal@sandflow.com>
Subject: [FFmpeg-devel] Re: [RFC] dormant tickets
Date: Tue, 23 Sep 2025 16:03:10 -0700
Message-ID: <CAF_7JxCd6LDijgCVrPDqGtUVOsPmKuFAbLULyyVRb+7wroybtQ@mail.gmail.com> (raw)
In-Reply-To: <20250923225736.GY29660@pb2>
On Tue, Sep 23, 2025 at 3:58 PM Michael Niedermayer via ffmpeg-devel
<ffmpeg-devel@ffmpeg.org> wrote:
>
> Hi
>
> Should tickets which are inactive be closed with a new resolution:dormant?
IMHO tickets should not be closed until resolved with a clear
rationale -- a resolution can be "will not fix" or "not germane" of
course.
What problem(s) are we trying to solve beyond the vague "[some] people
dont like old issues"?
I, for one, do not mind old issues as long as they are still relevant
-- it saves me from searching both open and closed issues and
differentiating between closed (resolved) and closed (dormant).
>
> If yes, should this be done to new and or open tickets ?
> and after what time ?
>
> its easy to do with trac
>
> (iam not saying that is a good idea, a bug is a bug and wont fix itself
> but it felt in the comments about trac / forgejo migration that people
> dont like old issues)
>
> and this question, i think captures this better than a migrate vs not migrate
> question
>
> IMHO, we should pay someone to go over the new tickets and open valid
> ones and close invalid ones and ask for more info in incomplete ones.
> independant of the tracker and independant of the handling of dormant tickets
>
> thx
>
> --
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Many that live deserve death. And some that die deserve life. Can you give
> it to them? Then do not be too eager to deal out death in judgement. For
> even the very wise cannot see all ends. -- Gandalf
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-09-23 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 22:57 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-23 23:03 ` Pierre-Anthony Lemieux via ffmpeg-devel [this message]
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=CAF_7JxCd6LDijgCVrPDqGtUVOsPmKuFAbLULyyVRb+7wroybtQ@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
--cc=pal@sandflow.com \
/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 http://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/ http://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