From: Michael Niedermayer <michael@niedermayer.cc> To: Jan Engelhardt <jengelh@inai.de> Cc: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] FFmpeg 5.0 Date: Mon, 31 Oct 2022 15:33:31 +0100 Message-ID: <20221031143331.GQ4321@pb2> (raw) In-Reply-To: <ss9225p7-9rpo-r229-5914-4n555p66sos@vanv.qr> [-- Attachment #1.1: Type: text/plain, Size: 2942 bytes --] Hi On Mon, Oct 31, 2022 at 02:26:25PM +0100, Jan Engelhardt wrote: > > On Sunday 2022-10-30 21:16, Michael Niedermayer wrote: > >> > >> Fedora 36 still uses FFmpeg 5.0 as I discovered there was an ABI break > >> that made upgrading to FFmpeg 5.1 not possible for F36. FFmpeg 5.1 is > >> used for Fedora 37, though. > > > >why is > >https://trac.ffmpeg.org/wiki/Downstreams > >not listing any of that ? > > It does not scale. > There are over 260 distros. Many of them have over 10000 packages. And > many have a rapid update cadence. The question is how many packages X Distros have security/update support Because if there is no security support you need nothing to add to the wiki and if there is, well that security/update support will take a human more time than to say that (s)he is doing that support for that package which is what the wiki lists > > You cannot expect distros to spend time updating other people's > wikis all the time. There is also no standardization and no automation. I dont expect that, if you dont expect us to make updated releases. This is a service we provide for you. If its too much for you to tell us you need/want/would benefit from a new release on a branch. Then you know, thats ok with me. > > If you want to know what versions are being shipped, confer with > information aggregatation projects such as repology, e.g. > https://repology.org/project/ffmpeg/versions Thats not the question i have. Some distro might ship 5.0.1 or 2.8.5 but that doesnt mean they would benefit from a 2.8.7 or 5.0.2. You can surely see that just by the fact that there are distros which never shipped updated versions of FFmpeg. For me the question is, should i make a new X.Y.Z+1. Or the other way around, is there a distro which actively maintains their FFmpeg X.Y package and wants/needs/would make a new package of that. the Downstreams list worked quite well for that for many years. Also E-mail and IRC have been quite effective. If it misses 50 or even 90% of distros that doesnt even matter as long as it lists a distro that maintains support for the same version. If i imagine that we would be concentrating on doing releases for every branch listed somewhere on repology for FFmpeg i do not think that would be an improvment. It would result in a lot of releases noone used and more delay in releases people would use. If you wish to automate part of this or improve the process sure, go ahead. But first step is to understand what this is trying to do, reading your mail makes me belive that you misunderstood this somewhat Thanks [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If you fake or manipulate statistics in a paper in physics you will never get a job again. If you fake or manipulate statistics in a paper in medicin you will get a job for life at the pharma industry. [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-10-31 14:33 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-28 18:23 Michael Niedermayer 2022-10-28 19:10 ` Timo Rothenpieler 2022-10-28 20:17 ` AV Preservation by reto.ch (lists) 2022-10-29 18:29 ` Neal Gompa 2022-10-29 19:42 ` Timo Rothenpieler 2022-10-30 20:10 ` Michael Niedermayer 2022-10-30 21:04 ` Neal Gompa 2022-10-31 13:03 ` Anton Khirnov 2022-10-31 17:51 ` Andreas Schneider 2022-11-03 22:23 ` Michael Niedermayer 2022-10-30 20:16 ` Michael Niedermayer 2022-10-30 20:53 ` Neal Gompa [not found] ` <ss9225p7-9rpo-r229-5914-4n555p66sos@vanv.qr> 2022-10-31 14:33 ` Michael Niedermayer [this message] 2022-11-03 22:28 ` Michael Niedermayer
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=20221031143331.GQ4321@pb2 \ --to=michael@niedermayer.cc \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=jengelh@inai.de \ /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 https://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/ https://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