[postgis-devel] Change all stable branch versions to have git hash?
Regina Obe
lr at pcorp.us
Tue Jan 7 16:10:31 PST 2020
I noticed that stable-3.0 branch reads this
Postgis 3.0.1dev - r17988 - 2020-01-07 23:42:39
SELECT postgis_full_version();
While r17988 is newer than released 3.0.0 r17983
I suspect it's just a number frozen in time.
Is there any reason why we can't have it read a git hash like master branch
does?
Master branch gives me - although the hash I finder harder to make sense of
what's newer and older, it's always nice to reference back specific released
commit.
POSTGIS="3.1.0dev r64d4a1a69" [EXTENSION] PGSQL="120"
GEOS="3.8.0-CAPI-1.13.1 " PROJ="6.2.1" LIBXML="2.9.9" LIBJSON="0.12"
LIBPROTOBUF="1.2.1" WAGYU="0.4.3 (Internal)"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20200107/ff60cb4d/attachment.html>
More information about the postgis-devel
mailing list