Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] trac ticket statistics Was: Re: Re: [RFC] Issue tracker
Date: Tue, 23 Sep 2025 23:50:17 +0200
Message-ID: <20250923215017.GW29660@pb2> (raw)
In-Reply-To: <236bc5ba-f7dd-4080-9ce2-1830dd38912b@gyani.pro>


[-- Attachment #1.1: Type: text/plain, Size: 1906 bytes --]

Hi Gyan

On Tue, Sep 16, 2025 at 10:09:14AM +0530, Gyan Doshi via ffmpeg-devel wrote:
> 
> 
> On 2025-09-16 03:16 am, Michael Niedermayer via ffmpeg-devel wrote:

[...]

> > And what do we gain by avoiding "wholesale migration" ?
> 
> Added bloat of thousands of dormant issues marked as open, many of which are
> invalid after these many years.

This is not an accurate description of the situation

If you look at trac, there are
 690    open tickets
 176    reopened tickets
2307    new tickets
5033    fixed tickets
1751    invalid tickets
 280    wont fix tickets
 565    duplicate tickets
 266    non reproduceable tickets
 593    tickets waiting for user input

What you can see here, is there are only 690 open tickets, that is not thousands

there are also 593 Tickets marked as needs_more_input,
these should not end on a read only system


We can also look at the last modified dates on tickets

last modified:
new (re)open
337    104      in 2024-09-23 to 2025-09-23
353     80      in 2023-09-23 to 2024-09-23
328     93      in 2022-09-23 to 2023-09-23
159     59      in 2021-09-23 to 2022-09-23
162     66      in 2020-09-23 to 2021-09-23
141     74      in 2019-09-23 to 2020-09-23
145     36      in 2018-09-23 to 2019-09-23
132     35      in 2017-09-23 to 2018-09-23
139     61      in 2016-09-23 to 2017-09-23
130     75      in 2015-09-23 to 2016-09-23

we have ATM 2307 new tickets, 1018 of these are
from the last 3 years.

I dont think droping all this, achieves anything positive.
You will have the same number of new tickets within 2-3 years, and
loss of past analysis/work on these issues.

thx

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Complexity theory is the science of finding the exact solution to an
approximation. Benchmarking OTOH is finding an approximation of the exact

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 163 bytes --]

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

  reply	other threads:[~2025-09-23 21:50 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                   ` Michael Niedermayer via ffmpeg-devel [this message]
2025-09-24 10:56                     ` [FFmpeg-devel] Re: trac ticket statistics Was: " 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
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=20250923215017.GW29660@pb2 \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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