From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 5.0 LTS vs 5.1 LTS
Date: Mon, 25 Apr 2022 19:19:46 +0200
Message-ID: <20220425171946.GY2829255@pb2> (raw)
In-Reply-To: <9c39d56f-9cf0-4f81-9e13-4bc1034cac3b@beta.fastmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 913 bytes --]
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.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Does the universe only have a finite lifespan? No, its going to go on
forever, its just that you wont like living in it. -- Hiranya Peiri
[-- 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-04-25 17:19 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 [this message]
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=20220425171946.GY2829255@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