Re: pgrouting updated to version 2.2.0-1.pgdg+1 - Mailing list pgsql-pkg-debian

From Sebastiaan Couwenberg
Subject Re: pgrouting updated to version 2.2.0-1.pgdg+1
Date
Msg-id 571694F9.6040400@xs4all.nl
Whole thread Raw
In response to Re: pgrouting updated to version 2.2.0-1.pgdg+1  (Vicky Vergara <vicky@georepublic.de>)
List pgsql-pkg-debian
On 04/19/2016 10:18 PM, Vicky Vergara wrote:
> oh, I didnt know that, sorry!!!.

No problem, these kind of issues are not the end of the world.

> So I need to name the tag 2.2.1 to be 2.2.2
> and recover the hash from 2.2.1 and tag it again, is that correct?

Yes, ideally the old 2.2.1 tag is restored to reference the old commit,
and the new 2.2.1 tag needs to be replaced with 2.2.2, but you'll likely
need to change a couple of source files to use 2.2.2 first too.

Deleting the new 2.2.1 tag and recreating it to reference the old commit
should suffice. You'll need to use `git push --tags -f` if you don't
explicitly remove the tag from the repository on GitHub first.

Documenting the release procedure in a HOWTORELEASE file is probably a
good idea so you and others don't have to remember the exact process.
Have a look at the PDAL document for inspiration:

 https://github.com/PDAL/PDAL/blob/master/HOWTORELEASE.txt

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1


pgsql-pkg-debian by date:

Previous
From: Christoph Berg
Date:
Subject: Re: pgrouting updated to version 2.2.0-1.pgdg+1
Next
From: Sebastiaan Couwenberg
Date:
Subject: Re: pgrouting updated to version 2.2.0-1.pgdg+1