http://semver.org

Currently we are using a non-semver semantic versioning since we have
the rule to not backport features in the release branch.

It warrants quite boring updates and distributors can stay happy not
being afraid of random changes breaking API and ABI as long they stick
to the right version and keep it.

On top of that integrators can just rely on pkgconf to check for feature
presence. (and do that the lazy way by just checking the minor and
ignoring the major and it is always wrong).

If we switch to semver the main changes would be making sure integrators
check both version numbers, have a diverging APIChange and have our
global version report as 11.0.1 instead of 11.1 and 11.1.0 if we add
compatible features mid-release.

Right now I'd rather *NOT* do that since we are already too busy, but
might be a good idea keep it in mind.

lu
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to