Also, they've recommended we switch to gitlab as the source since github is just a read-only mirror.
EDIT: from psi29a on discord:
gitlab is the 'truth', github is the mirror.
We've trying to deprecate/remove github for awhile now.
So all package maintainers should be using gitlab.
Anyway, git describe only shows annotated tags
it seems that we only had one annotated tag, and that was 0.43
debian doesn't use git describe
it just grabs tags and sorts
I believe that archlinux shouldn't rely on git describe for ground truth of latest release.
btw, how we develop... before we release, we branch from master... so for example, for 0.46 we branched... and continued polishing that branch.
That way we can continue developing on master towards 0.47 while 0.46 matures.
Since git describe only shows tags that can be reached via master...
it shouldn't be showing anything
0.43 is a fluke
Pinned Comments
bwrsandman commented on 2016-09-24 14:59
Please refrain from flagging the git version as out date when a new release comes out. The git aur packages update their version on install time based on the tags of the git repo.
Keep in mind that this is a VCS package and it is meant to be in line with the latest master which might not always work. It is not meant to follow the release pattern in any particularly smart way and assumes that upstream maintains their tags consistently.
For the newest release, the correct page is https://www.archlinux.org/packages/?q=openmw