On Mon, 2020-02-24 at 18:13 +0100, Miro HronĨok wrote:
On 24. 02. 20 17:48, Pierre-Yves Chibon wrote:
> However, for the release field, we are struggling a little bit
> more, two options
> are more appealing to us:
Can we please have a "git is the only source of truth" version of
this? I.e.
"Compute the release field from the number of commits since the last
version
change" in the document. It seem to only have one con (breaks if two
builds are
triggered from the same commit) which is the status quo.
The <#commits>.<#builds> approach also doesn't address
"snapshot"
prereleases, i.e. which can't be dealt with having appending
"~prereleasename" to the version, which is a second con (or a "pro"
of
the "try to emulate traditional manual release numbers" approach, if
you will).
Nils
--
Nils Philippsen "Those who would give up Essential Liberty to
Software Engineer purchase a little Temporary Safety, deserve neither
Red Hat Liberty nor Safety." -- Benjamin Franklin, 1759
PGP fingerprint: D0C1 1576 CDA6 5B6E BBAE 95B2 7D53 7FCA E9F6 395D
old: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011