[FFmpeg-devel] FFmpeg 7.0 blocking issues

Frank Plowman post at frankplowman.com
Fri Mar 8 17:04:17 EET 2024


On 08/03/2024 14:04, James Almer wrote:
> On 3/8/2024 11:02 AM, Kieran Kunhya wrote:
>> On Fri, 8 Mar 2024 at 14:00, James Almer <jamrial at gmail.com> wrote:
>>
>>> On 3/3/2024 4:35 AM, Jean-Baptiste Kempf wrote:
>>>>
>>>> n Sat, 2 Mar 2024, at 23:55, Michael Niedermayer wrote:
>>>>> On Tue, Jan 23, 2024 at 08:22:41PM +0100, Michael Niedermayer wrote:
>>>>>> 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
>>>>>
>>>>> We still have 3 blocking issues on trac
>>>>>
>>>>> do people want me to wait or ignore them and branch ?
>>>>
>>>> I think you can branch soon.
>>>> However, those 3 bugs are quite important, tbh.
>>>
>>> The bump and the AVOption changes were already applied, so IMO we can
>>> branch.
>>> The two remaining issues should not be blocking as they can be
>>> backported to 7.0 in a point release.
>>>
>>
>> VVC experimental flag is blocking.
>>
>> Kieran
> 
> Is there a patch for that?

There is this:
https://ffmpeg.org//pipermail/ffmpeg-devel/2024-February/321060.html
(missing from patchwork for some reason), but it looks like it causes
FATE to fail as is.


More information about the ffmpeg-devel mailing list