To prevent version issues for packagers, I will remove the -rc2 tag from
the source repo and change the default (when git is not found) version
string to 5.0.0-rc1-unknown to indicate that the version is somewhere
between rc1 and rc2.  I don't know that this makes things any clearer or
not but I'm pretty sure no matter what we do, someone will be confused.
I'm not really interested in making the cmake version string code any
more complicated so unless there are some options to `git describe` that
would make things clearer, I'm going to stick with the current code.

On 3/13/2018 12:18 PM, Carsten Schoenert wrote:
> Am 13.03.2018 um 17:05 schrieb Eeli Kaikkonen:
>> 2018-03-13 17:44 GMT+02:00 Jon Evans <>:
>>> I know what the G means, just wish git describe had an option to disable
>>> it, since it makes copy/paste more tedious.
>>> I think if we had left the tag at rc1, then we'd just have users thinking
>>> they had rc1 when they really have a newer nightly. Better to make a new
>>> tag that doesn't include rcN in it, or at least tries to make it a lot more
>>> obvious that it isn't a RC version despite having those letters in the
>>> string.
>> In a project where I took part in we solved a similar problem by using
>> {previous-tagged-version-number}+{version-control-reference}, for example
>> 5.0RC1+gitXXXXX. We felt the plus sign is less ambiguous.
> That would be the correct way and done by a lot of projects.
> The now additional tag -rc2-dev makes it more difficult for
> distributions to determine if a new version is available.
> -rc2* is greater as -rc1 and I'd need to tune the watch file again in
> Debian we use (and it's already a bit more complicated due the dfsg + rc
> part). The added tag -rc2-dev solves nothing and shouldn't be used in
> future situations.

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to