Re: [FFmpeg-devel] [PATCH 3/3] doc/developer.texi: add a section on API/ABI compatibility

[Stefano Sabatini <stefasab@gmail.com>]

On date Wednesday 2023-03-15 15:07:46 +0100, Anton Khirnov wrote:
> Document established practices in it.
> ---
>  doc/developer.texi | 162 ++++++++++++++++++++++++++++++++++++++++-----
>  1 file changed, 146 insertions(+), 16 deletions(-)
> 
> diff --git a/doc/developer.texi b/doc/developer.texi
> index 5e283227be..c625a9feed 100644
> --- a/doc/developer.texi
> +++ b/doc/developer.texi
> @@ -217,6 +217,7 @@ int myfunc(int my_parameter)
>  ...
>  @end example
>  
> +@anchor{Naming conventions}
>  @section Naming conventions
[...]  
> +
> +@anchor{Major version bumps}
> +@subsection Major version bumps
> +A major version bump signifies an API and/or ABI compatibility break. To reduce
> +the negative effects on our callers, who are required to adapt their code,
> +backward-incompatible changes during a major bump should be limited to:
> +@itemize @bullet
> +@item
> +Removing previously deprecated APIs.
> +
> +@item
> +Performing ABI- but not API-breaking changes, like reordering struct contents.
> +@end itemize
> +

This sounds a bit ambiguous. What qualifies "previously deprecated
APIs"? It looks to me that the current practice is to drop deprecated
symbols after 2 major bumps, so that users have the opportunity to
adapt their code depending on the deprecations warnings before the
deprecated symbols are finally removed at the next bump. If that's so,
maybe this can be formalized here.

[...]

LGTM otherwise, thanks.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".