Status: Unconfirmed
Owner: ----
New issue 1757 by ferd...@
gmail.com: Changelogs no longer mention ABI breaks
https://bugs.chromium.org/p/webm/issues/detail?id=1757Up through the release of 1.7.0, the CHANGELOG file for libvpx was diligent about mentioning when a release included an ABI break — in fact, generally, the very first line of the "Upgrading" section read:
"This release is ABI incompatible due to..."
Starting with release 1.8.0, though, and continuing through the three ABI breaks since, the authors of the CHANGELOG apparently fell out of this habit. This has led to issues in at least one downstream package collection (MSYS2), where the necessary dependent rebuilds weren't done following an ABI-breaking libvpx upgrade.
(See:
https://github.com/msys2/MINGW-packages/pull/8282)
The most recent release, 1.11.0 — which again includes an ABI break (ref: commit 4ec84326cc65c5b042bf06d222d51e51d7e5461d) — was in fact described in the CHANGELOG as a "maintenance release", which to my mind is the /opposite/ of an ABI-breaking update.
It is, of course, not the libvpx maintainers' responsibility to ensure that downstream dependent packages are rebuilt, nor would I ever ask them to take on that responsibility. My request is merely that the maintainers resume providing the explicit notifications that were made previously, and which would be helpful to projects that include libvpx in their software or collections.
Would it be possible for the maintainers to fall back _into_ the habit of explicitly declaring when releases are ABI-incompatible, so that downstream packagers will be prompted to rebuild their libvpx dependencies after updating the library? It would be much appreciated.
--
You received this message because:
1. The project was configured to send all issue notifications to this address
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings