Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Gyan Doshi <ffmpeg@gyani.pro>
Subject: [FFmpeg-devel] Re: trac ticket statistics Was: Re: Re: [RFC] Issue tracker
Date: Sun, 28 Sep 2025 11:43:13 +0530
Message-ID: <7e099f4c-7152-445b-bdd0-d743c6c6daba@gyani.pro> (raw)
In-Reply-To: <20250928004434.GZ29660@pb2>



On 2025-09-28 06:14 am, Michael Niedermayer via ffmpeg-devel wrote:
>>> What you can see here, is there are only 690 open tickets, that is not thousands
>> The oldest 'new' ticket is from 2013, so that label is misleading.
> They are "new" in the sense that they have not been categorized between
> valid+open and invalid+closed
>
>> It should be possible to revive them but on a case-by-case basis.
> That is only possible, if we have a volunteer to do that. Iam not sure
> who that would be.

If there is a volunteer, they can categorize tickets on trac and then we 
migrate the open & valid tickets and avoid bloat.
If there is no volunteer, then after migration, they will still remain 
dormant on the new tracker and become bloat.

As long as human attention is the bottleneck, I don't see the value in 
adding jetsam to the new tracker.

Regards,
Gyan
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-09-28  6:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-14 21:23 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-15 11:09 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-15 11:37   ` Michael Niedermayer via ffmpeg-devel
2025-09-15 12:06   ` Timo Rothenpieler via ffmpeg-devel
2025-09-15 12:30     ` Michael Niedermayer via ffmpeg-devel
2025-09-15 12:47       ` Timo Rothenpieler via ffmpeg-devel
2025-09-15 12:57     ` Michael Niedermayer via ffmpeg-devel
2025-09-15 13:05       ` Michael Niedermayer via ffmpeg-devel
2025-09-15 17:19       ` Timo Rothenpieler via ffmpeg-devel
2025-09-15 18:26         ` Michael Niedermayer via ffmpeg-devel
2025-09-15 18:35           ` Timo Rothenpieler via ffmpeg-devel
2025-09-15 19:09             ` Gyan Doshi via ffmpeg-devel
2025-09-15 21:46               ` Michael Niedermayer via ffmpeg-devel
2025-09-16  4:39                 ` Gyan Doshi via ffmpeg-devel
2025-09-23 21:50                   ` [FFmpeg-devel] trac ticket statistics Was: " Michael Niedermayer via ffmpeg-devel
2025-09-24 10:56                     ` [FFmpeg-devel] " Gyan Doshi via ffmpeg-devel
2025-09-28  0:44                       ` Michael Niedermayer via ffmpeg-devel
2025-09-28  6:13                         ` Gyan Doshi via ffmpeg-devel [this message]
2025-09-23 22:33                   ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-09-15 22:36             ` Michael Niedermayer via ffmpeg-devel
2025-09-28  7:54 ` Rémi Denis-Courmont via ffmpeg-devel
2025-09-28  8:51   ` Michael Niedermayer via ffmpeg-devel
2025-09-28 11:32     ` Rémi Denis-Courmont via ffmpeg-devel
2025-09-28  9:18   ` Michael Niedermayer via ffmpeg-devel
2025-09-28  9:59     ` Jacob Lifshay 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=7e099f4c-7152-445b-bdd0-d743c6c6daba@gyani.pro \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=ffmpeg@gyani.pro \
    /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