[postgis-devel] postgis 2.2.0 tag?

[Paragon Corporation]

FWIW: github does keep track of our tags too, though it's much messier

 

https://github.com/postgis/postgis/tree/2.2.0

 

But as Paul mentioned, github is just a mirror and SVN is still our primary repo.

 

The official tar balls are always listed on: http://postgis.net/source/

 

Thanks,

Regina

 

 

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
Sent: Thursday, November 05, 2015 5:11 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>; John Harvey <john.harvey at crunchydata.com>
Subject: Re: [postgis-devel] postgis 2.2.0 tag?

 

John,

Our official repository is svn, and the tag is here https://svn.osgeo.org/postgis/tags/2.2.0/


The github repo is just a mirror, and I’m not sure how/if it is supposed to reflect the tagging in svn

We only have some minor topology fixes sitting in the 2.2 branch right now, so no current pressure to drop a 2.2.1 in the short term

Thanks!

P 

On November 5, 2015 at 2:08:43 PM, John Harvey (john.harvey at crunchydata.com <mailto:john.harvey at crunchydata.com> ) wrote:

Hello, 

 

I noticed that when 2.2.0 was released, there was a source tarball created and a branch was made, but I couldn't find a tag that indicates which specific commit is tied to the release itself.  My current process it to clone the code with git, checkout the latest tag available, and then build with it.  As of now, there are no 2.2.x tags in the repository.

 

This may seem nitpicky, but the branch will live on for the life of 2.2, whereas a tag in my mind is a marker indicative of a specific regression-tested snapshot in time.  I want to make sure that I'm utilizing the release version that was published on October 7, /2015.  I did try chasing down the version by looking at the source tarball, but its corresponding change-log seems to indicate that it may have been generated before the 2.2.0 branch was created.  So, I thought I would ask the question to the experts.

 

I don't want to be a bother; I was just curious if this was something that could easily be remedied.

 

On a side note, is there a 2.2.1 planned in the near future, or is that a ways off?

 

Thank you for your time.

 

Best regards,

  -John

_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
http://lists.osgeo.org/mailman/listinfo/postgis-devel

-- 
Paul Ramsey
Sent with Airmail

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20151106/bc888f7c/attachment.html>