From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] FFmpeg 5.0 LTS vs 5.1 LTS Date: Mon, 25 Apr 2022 15:38:48 -0300 Message-ID: <f098be5f-e54d-f330-e599-2e24bf53483e@gmail.com> (raw) In-Reply-To: <20220425171946.GY2829255@pb2> On 4/25/2022 2:19 PM, Michael Niedermayer wrote: > On Mon, Apr 25, 2022 at 01:51:26PM +0200, Jean-Baptiste Kempf wrote: >> On Sat, 23 Apr 2022, at 18:36, Michael Niedermayer wrote: >>> Do people prefer that 5.0 becomes LTS or the next (5.1) ? >>> Or something else ? >> >> My understanding of the consensus was; >> - 5.0 in Dec/Jan >> - 5.1 in Jul with API additions, but no ABI/behavior breakage > > yes > > >> - 6.0 in Dec 22 with ABI/API/behavior breakage and while 5.1 becomes LTS > > we could give 5.1 an LTS "tag" when its released already > also thers the possibility that by december we have nothing that really > benefits from a ABI/API/behavior breakage. > If that happens people might prefer 5.2 over 6.0 i dont know. An ABI bump doesn't need to be justified by the need to break something for the sake of an addition, like new fields to structs with ABI-tied size (of which there are not many, for that matter). It could simply be done in an scheduled manner to get rid of deprecated stuff that's old enough to be dropped, giving the project some predictability, and keeping the tree clean-ish. > > thx > > [...] > > > _______________________________________________ > 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".
prev parent reply other threads:[~2022-04-25 18:39 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 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 [this message]
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=f098be5f-e54d-f330-e599-2e24bf53483e@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