[FFmpeg-devel] [PATCH 00/26] Major library version bump

[Marvin Scholz]

On 21 Jan 2023, at 21:17, Hendrik Leppkes wrote:

> On Sat, Jan 21, 2023 at 8:33 PM Marvin Scholz <epirat07 at gmail.com> wrote:
>>>
>>> Alternatively, we could just not have an instability period at all.
>>>
>>
>> Not having any instability period at all seems like a bad idea.
>>
>
> Actually that sounds like the best idea. You would just have to
> prepare the bump in a branch and all unstable changes ready to merge
> in an instant.
> Miss it? Tough. Having months long periods so people can get their
> stuff sorted is way too long. Ideally it should be prepared ahead of
> time and only a "soft instability" period of maybe two weeks reserved
> for bug fixes (don't want to sit on issues for ever), rather then big
> changes or new features.
>

How would it work? If I now make a branch with a breaking
change, where would I put it and how would I get it merged together with
the other breaking changes?

Or do you mean that there should be a public devel branch where API/ABI
breaking patches can be proposed for that will eventually be merged into
master at a defined point in time together with major bump?

> - Hendrik
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request at ffmpeg.org with subject "unsubscribe".