On 2025-09-16 03:16 am, Michael Niedermayer via ffmpeg-devel wrote:
What can happen is that if an existing open trac issue is taken up for
active resolution, then a new issue at Forgejo can be opened, with a
reference to the trac issue. A comment can be left at trac linking to this
new Forge issue, so all further activity occurs at code.ffmpeg. This would
avoid any wholesale migration or duplication.
It can _IF_ someone spends the extra time and work.
How many people want to do that ?
And how many will do it ?
There's hardly any extra work.
Open a single issue at forge where the title says, "trac 1234:
regression in ..."
Add a link to the trac issue in the body.
Post a comment at the trac issue: "continued at
https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/12345";
Only do this for issues where someone is actively handling the ticket.
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.
Regards,
Gyan
_______________________________________________
ffmpeg-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
