From: James Almer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: James Almer <jamrial@gmail.com>
Subject: [FFmpeg-devel] Re: FFmpeg 8.1 and 9.0
Date: Wed, 26 Nov 2025 20:01:11 -0300
Message-ID: <0b81fc6a-9ae0-4b90-85b6-55eb8325cefb@gmail.com> (raw)
In-Reply-To: <aSeCsA3N98QQrKG0@neo>
[-- Attachment #1.1.1: Type: text/plain, Size: 508 bytes --]
On 11/26/2025 7:44 PM, Michael Niedermayer via ffmpeg-devel wrote:
> Hi all
>
> I plan to branch and make 8.1 in February
> and 9.0 in May
Is 8.1 meant to be LTS? I forgot how the plan was in regards to that. I
recall 5.1 and 7.1 are considered LTS (Probably because of Debian).
Ubuntu will probably feature freeze 26.04, their LTS, around February.
It would be best if we align with them (They will most likely use either
8.0 or 8.1 if done in time, and I'd prefer them using the latter).
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-11-26 23:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 22:44 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-11-26 23:01 ` James Almer via ffmpeg-devel [this message]
2025-11-27 1:57 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-11-27 2:01 ` James Almer via ffmpeg-devel
2025-11-27 2:17 ` Lynne via ffmpeg-devel
2025-11-27 3:01 ` Michael Niedermayer via ffmpeg-devel
2025-11-27 12:28 ` Lynne via ffmpeg-devel
2025-11-28 1:19 ` Michael Niedermayer via ffmpeg-devel
2025-11-28 7:58 ` Lynne via ffmpeg-devel
2025-12-01 12:42 ` Michael Niedermayer via ffmpeg-devel
2025-12-01 12:57 ` Lynne via ffmpeg-devel
2025-12-01 23:39 ` Michael Niedermayer via ffmpeg-devel
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=0b81fc6a-9ae0-4b90-85b6-55eb8325cefb@gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=jamrial@gmail.com \
/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