https://bugzilla.redhat.com/show_bug.cgi?id=1971512
--- Comment #19 from Severin Gehwolf <sgehwolf(a)redhat.com> ---
Please use a better version scheme. Currently we have (uversion is very long.
too long, in fact[1]):
Version: 0
Release: 0.0.pre.2.%{uversion}%{?dist}
Upstream's latest tag is: v0.1-alpha. That's an unsortable version, but we
could do a bit better than just calling it 0. I see a 0.1 in there.
I suggest calling it 0.2 (for next upstream version) and following the snapshot
versioning scheme here:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_sn...
So something like this:
Version: 0.2
Release: 0.1.20210701gitc15dd4c%{?dist}
where 'c15dd4c' is output of `git rev-parse --short <sha>` of the revision
packaged. Then we get changelog entries like that:
* Thu Jul 1 2021 Jiri Vanek <jvanek(a)redhat.com> - 0.2-0.1.20210701gitc15dd4c
Thanks!
[1] $ echo 0.0.pre.1.c15dd4c19e81cbcefe419a99ebaa3af7c5c60c5e | wc -c
51
So it's 51 chars long where only 25 characters are recommended by
guidelines.
https://docs.fedoraproject.org/en-US/packaging-guidelines/Versioning/#_sn...
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component