From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 7.0 blocking issues
Date: Wed, 24 Jan 2024 08:40:36 +0100
Message-ID: <170608203677.8914.17390927215888357027@lain.khirnov.net> (raw)
In-Reply-To: <NoryLjo--3-9@lynne.ee>
Quoting Lynne (2024-01-23 21:18:29)
> Jan 23, 2024, 20:22 by michael@niedermayer.cc:
>
> > Hi all
> >
> > As it was a little difficult for me to not loose track of what is
> > blocking a release. I suggest that for all release blocking issues
> > open a ticket and set Blocking to 7.0
> > that way this:
> > https://trac.ffmpeg.org/query?blocking=~7.0
> >
> > or for the ones not closed:
> > https://trac.ffmpeg.org/query?status=new&status=open&status=reopened&blocking=~7.0
> >
> > will list all blocking issues
> >
> > Ive added one, for testing that, i intend to add more if i see something
> >
> > What is blocking? (IMHO)
> > * regressions (unless its non possible to fix before release)
> > * crashes
> > * security issues
> > * data loss
> > * privacy issues
> > * anything the commuity agrees should be in the release
> >
>
> On my side, what I want:
> Vulkan AV1. It's ready to be posted once the spec goes public very very soon.
> This shouldn't even become a blocker unless you want a release tagged immediately.
>
> And those that I don't consider as blockers, just something nice to have:
>
> Vulkan encode (H264). Needs about a week of work.
> HE-AAC 960-point.
> Preliminary xHE-AAC support. Not sure.
> AAC prepad fixes - perhaps partial (off by one sample for SBR).
Sigh. We already had this drama last time, must we do it again?
If you haven't even started working on it yet, then it shouldn't be a
blocker for the release, it can wait half a year for 7.1.
--
Anton Khirnov
_______________________________________________
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-01-24 7:40 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 19:22 Michael Niedermayer
2024-01-23 20:18 ` Lynne
2024-01-24 7:40 ` Anton Khirnov [this message]
2024-01-24 12:07 ` Lynne
2024-01-24 12:30 ` Anton Khirnov
2024-01-24 13:14 ` Lynne
2024-01-24 13:24 ` Anton Khirnov
2024-01-24 13:36 ` Lynne
2024-01-24 12:28 ` James Almer
2024-01-24 7:45 ` Anton Khirnov
2024-01-24 12:29 ` James Almer
2024-01-24 12:45 ` Niklas Haas
2024-01-28 10:38 ` Anton Khirnov
2024-01-24 13:59 ` Kieran Kunhya
2024-02-07 14:54 ` Derek Buitenhuis
2024-02-09 3:32 ` Michael Niedermayer
2024-02-12 15:36 ` Derek Buitenhuis
2024-02-07 18:49 ` Leo Izen
2024-02-07 18:56 ` Andreas Rheinhardt
2024-02-08 1:27 ` Leo Izen
2024-02-08 2:20 ` James Almer
[not found] ` <2E182D4F-95D4-43F7-A772-A737003B3C79@cosmin.at>
2024-02-07 18:55 ` Cosmin Stejerean via ffmpeg-devel
2024-02-10 21:03 ` James Almer
2024-02-11 1:35 ` Michael Niedermayer
2024-02-11 5:53 ` Nuo Mi
2024-02-25 23:18 ` Michael Niedermayer
2024-02-25 23:20 ` James Almer
2024-02-26 21:26 ` Michael Niedermayer
2024-03-02 22:55 ` Michael Niedermayer
2024-03-02 23:06 ` Sebastian Ramacher
2024-03-02 23:19 ` Michael Niedermayer
2024-03-03 1:39 ` Sean McGovern
2024-03-03 8:55 ` Sebastian Ramacher
2024-06-02 13:49 ` Sebastian Ramacher
2024-06-03 21:32 ` Michael Niedermayer
2024-06-03 21:36 ` Sean McGovern
2024-06-03 21:41 ` James Almer
2024-06-04 1:16 ` Michael Niedermayer
2024-06-04 7:23 ` Vittorio Giovara
2024-06-04 7:46 ` Anton Khirnov
2024-06-04 6:31 ` Rémi Denis-Courmont
2024-06-04 9:29 ` Sebastian Ramacher
2024-06-05 10:55 ` Kacper Michajlow
2024-06-04 8:34 ` Andrew Sayers
2024-06-04 9:19 ` Sebastian Ramacher
2024-03-03 7:35 ` Jean-Baptiste Kempf
2024-03-03 12:35 ` James Almer
2024-03-08 14:00 ` James Almer
2024-03-08 14:02 ` Kieran Kunhya
2024-03-08 14:04 ` James Almer
2024-03-08 15:04 ` Frank Plowman
2024-03-08 15:40 ` Kieran Kunhya
2024-03-09 12:33 ` Nuo Mi
2024-03-09 18:31 ` Marth64
2024-03-10 13:25 ` Xiang, Haihao
2024-03-10 23:29 ` Michael Niedermayer
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=170608203677.8914.17390927215888357027@lain.khirnov.net \
--to=anton@khirnov.net \
--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