v5.1.40 tag?

[Kevin Funk]

On Saturday, 16 September 2017 11:45:06 CEST René J.V. Bertin wrote:
> Hi,
> 
> I use project git tags and `git describe` for my package versioning.
> KDevelop's 5.2 branch was never yet tagged. I just tried to do
> 
> git tag v5.1.40 -m "Release 5.1.40" 6124c1319cc26dd61888aa8ed69b99ff7d44723a
> 
> so I can use something less obfuscated than 5.1.2.15137 as the package
> version for the 5.2 branch. I've done this kind of retro-active operation
> before for other projects (Konsole, for instance) but here it somehow
> doesn't have the intended effect. The tag is set, but the `git describe`
> result doesn't change. What am I missing, and maybe someone could do this
> in the central repo?

We never tag .40 versions, first tag will be the release candidate version -- 
which will pop up soon-ish.

.40 are no an official pin-pointed versions, something like "5.1.40" in 
CMakeLists.txt is merely for indicating we're "above" 5.1.x for e.g. the about 
dialog.

Regards,
Kevin

> Thanks,
> René


-- 
Kevin Funk | kfunk at kde.org | http://kfunk.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20170916/13aa84f1/attachment.sig>