From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] 7.0 blocking issues
Date: Mon, 25 Mar 2024 22:10:40 +0100
Message-ID: <20240325211040.GR6420@pb2> (raw)
In-Reply-To: <NtrGMcg--3-9@lynne.ee>
[-- Attachment #1.1: Type: text/plain, Size: 2013 bytes --]
On Mon, Mar 25, 2024 at 09:20:25PM +0100, Lynne wrote:
> Mar 25, 2024, 14:50 by ffmpeg@haasn.xyz:
>
> > On Mon, 25 Mar 2024 07:20:56 +0100 "Jean-Baptiste Kempf" <jb@videolan.org> wrote:
> >
> >> Hello,
> >>
> >> On Mon, 25 Mar 2024, at 01:03, Michael Niedermayer wrote:
> >> > Should i wait till all issues marked as blocking 7.0 on trac are fixed
> >> > before branching ?
> >>
> >> I think you should branch now.
> >> And get things fixed in the 7.0 branch.
> >>
> >
> > +1
> >
> > This is a big change and some breakage is inevitable. Most bugs will
> > probably only be found once the software is released and deployed.
> >
> > When a big milestone gets bogged down by months (if not years) of
> > "blocking bugs", my understanding is that it will simply never get
> > released, and users might as well resort to using git master / nightly
> > builds at that point.
> >
> > (Any possible allusion to *other* big open source software projects is
> > purely coincidental)
> >
>
> +1, we should branch so we can unblock master from receiving
ok, ill make the branch within the next 24h probably
We do have several open security issues still though (some have patches on the ML)
I still have to check if ossfuzz is hiding any issues in unrelated tickets
(ossfuzz did that often previously and this can unveil surprises)
Also iam behind with backporting security fixes to release branches,
(this may seem unrelated but it isnt because i always try to backport
each of my security fixes to all branches we still maintain at the same time,
so id like to get the other branches uptodate with backports to keep backports
in sync with a new 7.0)
All in all, iam not sure I will manage to release 7.0 in 7 days
but ill do the branch and we will see.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Those who are too smart to engage in politics are punished by being
governed by those who are dumber. -- Plato
[-- 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:[~2024-03-25 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 0:03 Michael Niedermayer
2024-03-25 0:35 ` James Almer
2024-03-25 2:30 ` Michael Niedermayer
2024-03-25 6:20 ` Jean-Baptiste Kempf
2024-03-25 13:50 ` Niklas Haas
2024-03-25 20:20 ` Lynne
2024-03-25 21:10 ` Michael Niedermayer [this message]
2024-03-25 21:18 ` Kieran Kunhya
2024-03-25 21:57 ` Michael Niedermayer
2024-03-25 21:29 ` 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=20240325211040.GR6420@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