[Rpm-maint] [rpm-software-management/rpm] Preparing for rpm 4.20.0-alpha2 (3b3c948)

[Panu Matilainen]

I haven't traditionally updated the library versions between pre-release stages even if and when the API changed a bit, and the code of course always changes. Basically I interpreted the "Update the version information only immediately before a public release of your software" in libtool version updating instructions per final release, so the info is only updated in the alpha (or so) release and not after that, basically because these pre-release versions are not something under longterm support so "we don't care". Of course there are several arguments to the contrary, certainly pre-releases are public releases too, updating for them is more technically correct and there aren't so many of them to considerably inflate the numbers. Just as a FYI/FWIW thing, in case you ever run into this in older releases and wonder :sweat_smile: 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/commit/3b3c94845abae7de138dcd0288842768575be9e8#r143450274
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/commit/3b3c94845abae7de138dcd0288842768575be9e8/143450274 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20240623/dda32dae/attachment-0001.html>