[FFmpeg-devel] FFmpeg 4.2

James Almer jamrial at gmail.com
Sun Aug 4 16:51:24 EEST 2019


On 8/4/2019 8:08 AM, Timo Rothenpieler wrote:
> On 04.08.2019 07:56, Michael Niedermayer wrote:
>> On Sun, Jul 21, 2019 at 07:11:40PM +0200, Michael Niedermayer wrote:
>>> On Mon, May 20, 2019 at 08:39:45PM +0200, Michael Niedermayer wrote:
>>>> Hi
>>>>
>>>> Its quite some time since 4.1 so its probably getting time to branch
>>>> 4.2.
>>>>
>>>> If there are any bugs you want fixed in 4.2 its probably a good idea to
>>>> fix them soon.
>>>>
>>>> Are there any suggestions for a name ?
>>>> If not ill pick something from unused past suggestions.
>>>>
>>>> If there are no objections i will likely make that release in the
>>>> next weeks
>>>
>>> 4.2 branch made
>>> i intend to make the 4.2 release from HEAD of release/4.2 in the next
>>> 1-2 weeks
>>> please backport any relevant bugfixes to it.
>>
>> Status update: There are a few remaining crashes / security issues
>> which i think
>> we should fix and include before the release. Iam working on that
>> currently.
>>
>> When thats done depends on
>> 1. any delays (bikesheds, distractions, headaches, good weather that
>> makes me ignore
>>     this and go for a walk or maybe going for a walk occasionally
>> actually helps
>>     my efficiency who knows, ...)
>> 2. influx of more security reports (fuzzer and any human reports),
>> there where
>>     several new reports in the last 2 weeks which fall in the "I think
>> that should
>>     be fixed before the release" category
>> 3. murphies law and anything else unexpected
>>
>> Thanks
> 
> I would kinda like to have the h263 hwaccel fix in for 4.2.
> It's a one line patch that unbreaks it for all hwaccel backends.

Just backport it. As long as it's not something that changes the API
with a version bump (Since that's already frozen in the release/4.2
branch), it should be fine.


More information about the ffmpeg-devel mailing list