uch as API breakages or adding new features (however using semver would
probably be most useful for consumers), there's just need to be an official
versioning scheme, and some eventual releases so people don't have to
reside to inventing snapshot schemes.
--
Dmitry Marakasov . 55B5 0596 FF1E
use consistent scheme. There's no need for
exact commit:version mapping, to say that "versions below x.y.z"
contain a bug or vulnerability. Just enough precision to not have
to wait months for a fixed version to be released.
> [1] https://git.savannah.gnu.org/cgit/poke.git/log/gnulib
> [2] https://git.savannah.gnu.org/cgit/gettext.git/log/gnulib
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: https://github.com/AMDmi3
r embedded in the source. You may as well embed git commit
or `git describe` output, but it should be clearly separated from the
version.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: https://github.com/AMDmi3
