On Mon, 20 Feb 2023, at 00:50, Neal Gompa wrote: > This is not a reasonable response, especially to someone who is > volunteering their time to develop features for a project. If it > misses 6.0, it sucks. > > My concern though is that major version bumps are supposed to be > ABI/API breaks, if this patchset doesn't land in 6.0, does that mean > it'd have to be pushed off to 7.0 if it makes public API changes? If > that's the case, I'd rather request 6.0 to be delayed to get this to land.
Adding an API call does not break the API. Adding an API can, in the large percentage of cases, be done without breaking ABI (Sure, it might means that the structures are not as beautiful as they should be, but...) I don't see the issue here. In general, adding big changes should be done at the beginning of a new cycle, not at the end. jb -- Jean-Baptiste Kempf - President +33 672 704 734 _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
