From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: FFmpeg 8.1 and 9.0
Date: Thu, 27 Nov 2025 02:57:46 +0100
Message-ID: <aSewGvbSE9Py9ezm@neo> (raw)
In-Reply-To: <0b81fc6a-9ae0-4b90-85b6-55eb8325cefb@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1131 bytes --]
Hi James
On Wed, Nov 26, 2025 at 08:01:11PM -0300, James Almer via ffmpeg-devel wrote:
> 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?
yes, iam kind of trying to maintain the last of each major version
but sometimes distros ship others and i maintain these then too
> I forgot how the plan was in regards to that.
same here, i cant remember either.
I do need an assistent who enjoys keeping track of these things and reminding me
> 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).
Do you know till when we need to make 8.1 then so its in ubuntu LTS ?
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Observe your enemies, for they first find out your faults. -- Antisthenes
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 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-27 1:58 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 ` [FFmpeg-devel] " James Almer via ffmpeg-devel
2025-11-27 1:57 ` Michael Niedermayer via ffmpeg-devel [this message]
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=aSewGvbSE9Py9ezm@neo \
--to=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
/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