Although, after all these years I still have to look up every single incantation except for the most basic things.
This "5.0 release" thread in the official mailing list shows that they are trying to establish a "feature freeze" process in order to have a clear cut point where a release branch is made:
http://ffmpeg.org/pipermail/ffmpeg-devel/2022-January/290665...
(yes that's the beginning of the thread... I guess the conversation drifted naturally from some previous patch discussion, until the point someone decided to change the email subject)
See "Big API changes and deprecations" to know more about the major version bump.
I just looked at the new features for 5.0.
Does anyone have a more detailed description on what these are?
So the above argument is not addressing the situation. Making bug reporting a better experience is in the interest of the project.
I find Debian bug reports a similarly annoying experience becasue it's so archaic. I.e. I deal with it, but I can totally understand if someone is turned off by the experience and simply avoids reporting bugs because of it.
I'm not sure if ffmpeg follows semver at all. I thought their API was pretty stable after the big change from "next_video_frame" (or whatever it was called) to the send/receive packet/frame model.
Could you explain what you did see in that link in a few simple words?