From: Jacob Lifshay <programmerjake@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 8.0 Release
Date: Fri, 01 Aug 2025 15:17:48 -0700
Message-ID: <85B207DE-B9A4-49C6-891B-36EDBA69628D@gmail.com> (raw)
In-Reply-To: <20250723114343.GK29660@pb2>
On July 23, 2025 4:43:43 AM PDT, Michael Niedermayer <michael@niedermayer.cc> wrote:
> 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'm expecting https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20024 to be merged soon since all the review comments were resolved on Wednesday. Can you (or someone else) please merge that before creating the release/8.0 branch? Of course that's all assuming there aren't any more review issues that need to be resolved.
Thanks,
Jacob
_______________________________________________
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-01 22:18 UTC|newest]
Thread overview: 18+ 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-07-25 15:50 ` Derek Buitenhuis
2025-08-01 22:17 ` Jacob Lifshay [this message]
2025-08-01 23:16 ` Romain Beauxis
2025-08-02 9:05 ` Niklas Haas
2025-08-02 9:19 ` Nicolas George
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=85B207DE-B9A4-49C6-891B-36EDBA69628D@gmail.com \
--to=programmerjake@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/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