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 and 9.0
Date: Fri, 28 Nov 2025 08:58:02 +0100
Message-ID: <18b82a5e-a049-4a77-a21c-b5661968b8b6@lynne.ee> (raw)
In-Reply-To: <aSj4pLh-6QTU55WL@neo>
On 28/11/2025 02:19, Michael Niedermayer via ffmpeg-devel wrote:
> Hi Lynne
>
> On Thu, Nov 27, 2025 at 01:28:10PM +0100, Lynne via ffmpeg-devel wrote:
>> On 27/11/2025 04:01, Michael Niedermayer via ffmpeg-devel wrote:
>>> Hi Lynne
>>>
>>> On Thu, Nov 27, 2025 at 03:17:34AM +0100, Lynne via ffmpeg-devel wrote:
>>>> On 26/11/2025 23:44, Michael Niedermayer via ffmpeg-devel wrote:
>>>>> Hi all
>>>>>
>>>>> I plan to branch and make 8.1 in February
>>>>> and 9.0 in May
>>>>
>>>> I'd like 8.1 in late December, and an 8.2 in late March.
>>>
>>> STF will possibly fund some of the work and that will not happen in december
>>
>> I don't get it? How is that related to a release?
>
> STF will possibly fund fixing fuzzer/security issues for a few months
> in 2026. So it makes sense to make releases when these issues are fewest
We can simply release a snapshot of what we have, it's just a tag after all.
_______________________________________________
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-28 7: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
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 [this message]
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=18b82a5e-a049-4a77-a21c-b5661968b8b6@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