From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] FFmpeg 5.0 Date: Sun, 30 Oct 2022 21:10:07 +0100 Message-ID: <20221030201007.GD1814017@pb2> (raw) In-Reply-To: <CAEg-Je8=6V7g4QjNhrWH_LAWj=vWTAWj5TQCkt0F9fuMrd0+Uw@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2402 bytes --] On Sat, Oct 29, 2022 at 02:29:56PM -0400, Neal Gompa wrote: > On Fri, Oct 28, 2022 at 2:23 PM Michael Niedermayer > <michael@niedermayer.cc> wrote: > > > > Hi > > > > According to our > > https://trac.ffmpeg.org/wiki/Downstreams > > > > Noone and nothing is using 5.0 > > should i make another release of 5.0 ? > > should i move 5.0 to olddownloads ? > > > > does anyone use it ? plan to use it or know of someone using it ? > > > > 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. > > This had apparently been also discovered by openSUSE some time ago: > https://build.opensuse.org/package/view_file/multimedia:libs/ffmpeg-5/work-around-abi-break.patch?expand=1 You can replace 5.0 by 5.1 but not 5.1 by 5.0, The compatibility is only in one way. Iam assuming here you talk about the addition of functions and there is not some other issue iam not aware of. > > Fedora 36 will still be supported until June, so I would appreciate it > if another release of 5.0 would be made. I have to admit i feel a bit undecided. Id like to first understand why this situation/"need" exists for fedora but not others > > Do we have ABI testing in place for submitted patches? I haven't seen > any evidence of CI testing of patches submitted to the mailing list, > but maybe I'm looking in the wrong place? If there is, maybe we can > consider adding some kind of ABI testing for release branches, using > tools like libabigail[1] with abidiff[2]? > > [1]: https://sourceware.org/libabigail/ > [2]: https://www.mankier.com/1/abidiff iam not sure there is agreement between you and others of what is a ABI break so the tool maybe will not help. I have generaly done testing with replacing old libraries by new when doing releases. But for me a ABI break is if replacing a library by another breaks some binary that is not rebuild and linked to the new lib. More testing is always good and welcome of course. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Breaking DRM is a little like attempting to break through a door even though the window is wide open and the only thing in the house is a bunch of things you dont want and which you would get tomorrow for free anyway [-- 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-30 20:10 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 [this message] 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 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=20221030201007.GD1814017@pb2 \ --to=michael@niedermayer.cc \ --cc=ffmpeg-devel@ffmpeg.org \ /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