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: Re: [FFmpeg-devel] FFmpeg 8.0 Release
Date: Wed, 20 Aug 2025 23:06:33 +0200
Message-ID: <20250820210633.GF29660@pb2> (raw)
In-Reply-To: <8f608a3c-b88a-4c97-9b54-640dd5ef1660@lynne.ee>
[-- Attachment #1.1: Type: text/plain, Size: 1329 bytes --]
Hi
On Wed, Aug 20, 2025 at 10:18:20AM +0900, Lynne via ffmpeg-devel wrote:
> On 20/08/2025 06:13, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi all
> >
> > On Fri, Aug 01, 2025 at 06:16:18PM -0500, Romain Beauxis wrote:
> > > Le mer. 23 juil. 2025 à 06:43, Michael Niedermayer
> > > <michael@niedermayer.cc> a écrit :
> > > >
> > > > Hi everyone
> > > >
> > > > I intend to create the release/8.0 branch in the next 1-2 weeks
> > > > after that i intend to make teh 8.0 release in the following 1-2 weeks
> > > >
> > > > If theres something you want in it make sure its pushed before the branch
> > > > is made.
> > >
> > > I would like to mention
> > > https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20026 as well.
> >
> > I intend to make the release in the nest 24-48h
> > so if nothing delays this, then thats as long as theres left to
> > make any changes to 8.0
>
> I'll write up a blog post as usual.
>
> It'll be quite long this time, as I'd like to mention in detail the work on
> Vulkan accelerated decoding and encoding, so if possible, I'd like to get
> the full 48 hours.
ok
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
It is dangerous to be right in matters on which the established authorities
are wrong. -- Voltaire
[-- 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:[~2025-08-20 21:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 11:43 Michael Niedermayer
2025-07-23 13:45 ` Timo Rothenpieler
2025-07-23 16:27 ` Michael Niedermayer
2025-07-23 16:43 ` Dimitry Andric
2025-07-23 17:48 ` Michael Niedermayer
2025-07-23 18:19 ` Jacob Lifshay
2025-07-24 0:16 ` Michael Niedermayer
2025-07-23 18:40 ` Nicolas George
2025-07-23 23:58 ` Michael Niedermayer
2025-07-23 14:01 ` Niklas Haas
2025-07-23 14:01 ` Niklas Haas
2025-07-24 0:38 ` James Almer
2025-07-25 15:34 ` Andrew Randrianasulu
2025-08-19 20:06 ` Michael Niedermayer via ffmpeg-devel
2025-07-25 15:50 ` Derek Buitenhuis
2025-08-01 22:17 ` Jacob Lifshay
2025-08-19 21:10 ` Michael Niedermayer via ffmpeg-devel
2025-08-01 23:16 ` Romain Beauxis
2025-08-19 21:13 ` Michael Niedermayer via ffmpeg-devel
2025-08-20 1:18 ` Lynne via ffmpeg-devel
2025-08-20 21:06 ` Michael Niedermayer via ffmpeg-devel [this message]
2025-08-21 15:33 ` Kacper Michajlow via ffmpeg-devel
2025-08-02 9:05 ` Niklas Haas
2025-08-02 9:19 ` Nicolas George
2025-08-04 8:13 ` Tobias Rapp
2025-08-04 8:16 ` Nicolas George
2025-08-06 5:47 ` Rémi Denis-Courmont
2025-08-08 16:45 ` Michael Niedermayer
2025-08-17 8:09 ` Rémi Denis-Courmont via ffmpeg-devel
2025-08-08 16:43 ` Michael Niedermayer
2025-08-08 23:24 ` Romain Beauxis
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=20250820210633.GF29660@pb2 \
--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