From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 9CFC04B7D1 for ; Wed, 24 Sep 2025 10:57:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ffmpeg.org; i=@ffmpeg.org; q=dns/txt; s=mail; t=1758711438; h=message-id : date : mime-version : to : references : in-reply-to : reply-to : subject : list-id : list-archive : list-archive : list-help : list-owner : list-post : list-subscribe : list-unsubscribe : from : cc : content-type : content-transfer-encoding : from; bh=/m5wqCOFSiNLKpqxOUhxvPWbpvKkfidoRqDJKfIzkHg=; b=UKLNgvV5aU4aAY4Q8e1ewuZduEWv8uSzjAMmZV9npFMJcMCQzorSMe6STMfR092V3OKME HjmCW6XYRL+epJHF1ujIBL7XQUzf8tNB2XwuK9qpqVM4nFJy4RHs3mO0vGii9w5ls9Um3c3 FIGSAwKsVAJm78kRkULkKQZl0CGgXpl6ROJ7GB96VYC+J9nNgoBRzbdjZ9GyKCFNSuuCW/J sPxfby+2XtfrYnR8eLfi/m61lbTE4tgxCtMmic33kYIw5AtZDmYZLLElUSHa/6GPsECRNlT HcR0LDp/ZSkY6m5AyJen7AMoFTqYJt4z4VMYkofbYOlNGXTsFGUY0km+mMtg== Received: from [172.19.0.4] (unknown [172.19.0.4]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 84EBF68EC6D; Wed, 24 Sep 2025 13:57:18 +0300 (EEST) ARC-Seal: i=1; cv=none; a=rsa-sha256; d=ffmpeg.org; s=arc; t=1758711434; b=gQ3ydRyHQmhMbN1/aNBOTjyR1+UAQAW7NVLJAU/F3bXGqxh9XNCxIn9ittHEKLML18JZ1 U0kzkgAsh9bbT3jmHOt6cehN2wx2oG+fb6tlHyaTce2ITXchsFnbYxgdeked5Gi3o0PWZYr YldrL64cLdo9Nps1vxy2YOIkxtGK+4NJaingGePJzvQElB2ptMwXY8V1r9QSAd1w91cjGbC QiVNhoa5943dOpiU9hk9atua5Djxyv9W+CvY6n1jm4TDUs3X2dl7Yl1BUXUzfStkNyh1ZUY HqZYUq1oSi5+czG55ctbNKlCc/3PZ4nYxXEbNS75PVyS9BKgLS9QP9vI8eBA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=ffmpeg.org; s=arc; t=1758711434; h=from : sender : reply-to : subject : date : message-id : to : cc : mime-version : content-type : content-transfer-encoding : content-id : content-description : resent-date : resent-from : resent-sender : resent-to : resent-cc : resent-message-id : in-reply-to : references : list-id : list-help : list-unsubscribe : list-subscribe : list-post : list-owner : list-archive; bh=PCVnlf2y80tNIprQeKK8RJfE6dTbRu7QAg7mExiNgDA=; b=qrhwit7pWnN2opUaPqpsxC0JqHRb5JxHglOeDk8t35XkdphgcaKnbQnFaBxdbo70S9HBG LPylzNdVJYWN6fT08pMDeTvbzEMC3w5158UXDPQvP2DgyXa7sosYyWmy0Nv9uy1taGEgHR+ bl6+P403Pd71Nze7PxPeG3K1SmsBmZQo3CyR8QVaiJUAHpUtKqMG0jAfHxAaoxRpI1zsZay qHugMIDbRtrOoN70+/MuPaKtIRehUG1Rf1wlMzFGoYkXcSKfmB7xB2T81b4ZM9jUcZ7Hj6O D5OUoNiYWvvVGUhyNlQ+8I1amzugB37ci58sQcogNUv47wGfI07x9M63R2Yw== ARC-Authentication-Results: i=1; ffmpeg.org; dkim=fail; arc=none; dmarc=none Authentication-Results: ffmpeg.org; dkim=fail; arc=none (Message is not ARC signed); dmarc=none Received: from mout-p-102.mailbox.org (mout-p-102.mailbox.org [80.241.56.152]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 1BBF868EC59 for ; Wed, 24 Sep 2025 13:57:01 +0300 (EEST) Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4cWv1Q4r4tz9tm5 for ; Wed, 24 Sep 2025 12:56:58 +0200 (CEST) Message-ID: <9d1c80e4-5dbe-47c5-a160-e5a546bc1435@gyani.pro> Date: Wed, 24 Sep 2025 16:26:53 +0530 MIME-Version: 1.0 To: ffmpeg-devel@ffmpeg.org References: <20250914212317.GG29660@pb2> <20250915110947.GH29660@pb2> <62f9da36-5260-49d3-8cf7-d59d6456fb0d@rothenpieler.org> <20250915125753.GK29660@pb2> <0d0942ee-82f9-4a40-a9c9-80f9cc00fe67@rothenpieler.org> <20250915182620.GM29660@pb2> <1298de15-af42-4280-b897-97aadab95087@rothenpieler.org> <612e19bf-919d-4a6b-8180-d7d655fbae83@gyani.pro> <20250915214608.GN29660@pb2> <236bc5ba-f7dd-4080-9ce2-1830dd38912b@gyani.pro> <20250923215017.GW29660@pb2> Content-Language: en-US In-Reply-To: <20250923215017.GW29660@pb2> Message-ID-Hash: CAN22OFIJW3Z4BKKCCI3F6IOKRADEERK X-Message-ID-Hash: CAN22OFIJW3Z4BKKCCI3F6IOKRADEERK X-MailFrom: SRS0=JG6B=4D=gyani.pro=ffmpeg@ffmpeg.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-ffmpeg-devel.ffmpeg.org-0; header-match-ffmpeg-devel.ffmpeg.org-1; header-match-ffmpeg-devel.ffmpeg.org-2; header-match-ffmpeg-devel.ffmpeg.org-3; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Content-Filtered-By: Mailman/MimeDel 3.3.10 X-Mailman-Version: 3.3.10 Precedence: list Reply-To: FFmpeg development discussions and patches Subject: [FFmpeg-devel] Re: trac ticket statistics Was: Re: Re: [RFC] Issue tracker List-Id: FFmpeg development discussions and patches Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: Gyan Doshi via ffmpeg-devel Cc: Gyan Doshi Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit Archived-At: List-Archive: List-Post: On 2025-09-24 03:20 am, Michael Niedermayer via ffmpeg-devel wrote: > 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 The oldest 'new' ticket is from 2013, so that label is misleading. By open, I meant unresolved tickets so that includes open + reopened + new + waiting for user input = 690 + 176 + 2307 + 593 = 3766 tickets. > there are also 593 Tickets marked as needs_more_input, > these should not end on a read only system It should be possible to revive them but on a case-by-case basis. The oldest 'needs_more_info' ticket #228 has its last activity in Dec 2013. There's no point in blindly migrating such tickets wholesale. Maybe it's possible to add a banner on trac so that when someone lands on a ticket, the banner tells them where they can open a new issue (on F) to report a brand-new issue or continue a trac ticket. A few of us can have permissions to update trac so that we can add a link to F if a ticket is revived. trac can then become read-only for the rest. Regards, Gyan _______________________________________________ ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org