From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] 5.0 blocking issues
Date: Sat, 8 Jan 2022 17:30:12 +0100
Message-ID: <20220108163012.GF2829255@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 731 bytes --]
Hi all
This is a simple go/no go call
if you know of something that still should go into 5.0 please reply here
with a list of what you are working on and a timelimit until when you
will be done with it
if you think everything is ready for the release, then too feel free to
reply (assuming few others said ok yet) this is not supposed to become a
100 reply thread with oks, just maybe 2-3 people confirming that noone
is aware of things missing.
I intend to do the release within 2-3 days of all "no go" things being
resolved or timeouting
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Opposition brings concord. Out of discord comes the fairest harmony.
-- Heraclitus
[-- 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 reply other threads:[~2022-01-08 16:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 16:30 Michael Niedermayer [this message]
2022-01-08 16:36 ` Romain Beauxis
2022-01-08 18:55 ` Soft Works
2022-01-08 21:31 ` Lynne
2022-01-10 3:09 ` "zhilizhao(赵志立)"
2022-01-10 9:04 ` lance.lmwang
2022-01-10 10:32 ` "zhilizhao(赵志立)"
2022-01-10 16:55 ` Anton Khirnov
2022-01-10 18:12 ` Andreas Rheinhardt
2022-01-12 6:37 ` Lynne
2022-01-12 16:30 ` Michael Niedermayer
2022-01-12 16:36 ` Nicolas George
2022-01-12 16:41 ` James Almer
2022-01-12 16:47 ` Nicolas George
2022-01-12 17:30 ` Jean-Baptiste Kempf
2022-01-12 17:58 ` Nicolas George
2022-01-12 23:17 ` Michael Niedermayer
2022-01-12 21:35 ` Soft Works
2022-01-13 4:02 ` Xiang, Haihao
2022-01-13 11:34 ` James Almer
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=20220108163012.GF2829255@pb2 \
--to=michael@niedermayer.cc \
--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