From: Lynne via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Lynne <dev@lynne.ee>
Subject: [FFmpeg-devel] Re: FFmpeg 8.1
Date: Fri, 20 Feb 2026 17:14:45 +0100
Message-ID: <aafa9c85-f41f-4b66-97b5-6a2f9a9cc8b4@lynne.ee> (raw)
In-Reply-To: <aYyLg9JDsN5EkU02@neo>
On 11/02/2026 15:00, Michael Niedermayer via ffmpeg-devel wrote:
> Hi Everyone
>
> I intend to branch release/8.1 in the next weeks, and i intend to have all
> reported fuzzer found security issues fixed in 8.1 (likely not all non security
> issues but more fixes is better)
> and i intend to have 8.1 made in march.
Could you wait for 2 weeks from now to branch it? That way, it'll come
out in mid-March, which is what you mentioned when I asked in December.
I'd like to merge the Vulkan ProRes encoder, otherwise the changelog is
just too short, and convert all filters to compile-time SPIR-V, so we
can finally drop the shaderc/glslang dependency and have all the Vulkan
code be fully usable with no external deps. But I need more time. 2
weeks will be enough.
_______________________________________________
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:[~2026-02-20 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 14:00 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2026-02-20 16:14 ` Lynne via ffmpeg-devel [this message]
2026-02-27 0:42 ` [FFmpeg-devel] " 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=aafa9c85-f41f-4b66-97b5-6a2f9a9cc8b4@lynne.ee \
--to=ffmpeg-devel@ffmpeg.org \
--cc=dev@lynne.ee \
/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