From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] FFmpeg 5.0 LTS vs 5.1 LTS Date: Sat, 23 Apr 2022 15:14:56 -0300 Message-ID: <c63f5593-2457-f9ad-f32c-74432dbecf77@gmail.com> (raw) In-Reply-To: <CAEg-Je9jySVfqeAu8S4FbhkZjVi9MfdbdLBf9EHVpbK1jhShTQ@mail.gmail.com> On 4/23/2022 3:08 PM, Neal Gompa wrote: > On Sat, Apr 23, 2022 at 12:40 PM James Almer <jamrial@gmail.com> wrote: >> >> On 4/23/2022 1:36 PM, Michael Niedermayer wrote: >>> Hi all >>> >>> Do people prefer that 5.0 becomes LTS or the next (5.1) ? >>> Or something else ? >>> >>> Thanks >> >> 5.0 lacks the new channel layout API, and making that an LTS will give >> projects less incentive to migrate, so IMO, 5.1 (or a newer one) should >> be the LTS. > > I thought 5.x was the LTS series already. Maybe I misunderstood, but I > expected that the 5.x series does not break API/ABI, so minor versions > of the 5.0 major series would be part of the same LTS and supported > for that timeframe. No 5.x release will break existing API/ABI, but all can and most likely will introduce new API. So if you target 5.0, you can use 5.x just fine. As an example, 5.1 will be the first with a new channel layout API in lavu, which will of course live alongside the old (now marked as deprecated) until a major bump takes place in a couple years. > > At least, that was my impression when I started bringing ffmpeg into Fedora... > > > > > -- > 真実はいつも一つ!/ Always, there's only one truth! > _______________________________________________ > 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". _______________________________________________ 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-04-23 18:15 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-23 16:36 Michael Niedermayer 2022-04-23 16:40 ` James Almer 2022-04-23 18:08 ` Neal Gompa 2022-04-23 18:14 ` James Almer [this message] 2022-04-23 18:17 ` Neal Gompa 2022-04-24 9:18 ` Gyan Doshi 2022-04-24 9:55 ` Steven Liu 2022-04-24 22:48 ` Soft Works 2022-04-25 8:01 ` Paul B Mahol 2022-04-25 9:04 ` Soft Works 2022-04-25 11:51 ` Jean-Baptiste Kempf 2022-04-25 17:19 ` Michael Niedermayer 2022-04-25 18:04 ` Jean-Baptiste Kempf 2022-04-25 18:40 ` Michael Niedermayer 2022-04-25 19:40 ` Soft Works 2022-04-25 19:44 ` Jean-Baptiste Kempf 2022-04-26 13:32 ` Michael Niedermayer 2022-04-25 18:38 ` James Almer
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=c63f5593-2457-f9ad-f32c-74432dbecf77@gmail.com \ --to=jamrial@gmail.com \ --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