Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ascJX-000082-F0 for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 19 Apr 2016 20:32:03 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1ascJX-0008S9-1j for pgsql-pkg-debian@arkaria.postgresql.org; Tue, 19 Apr 2016 20:32:03 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1ascGO-00075c-4I for pgsql-pkg-debian@postgresql.org; Tue, 19 Apr 2016 20:28:48 +0000 Received: from lb3-smtp-cloud3.xs4all.net ([194.109.24.30]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1ascGK-0002bA-4q for pgsql-pkg-debian@postgresql.org; Tue, 19 Apr 2016 20:28:47 +0000 Received: from [10.0.0.150] ([82.94.42.6]) by smtp-cloud3.xs4all.net with ESMTP id kLUh1s00907ytKE01LUioc; Tue, 19 Apr 2016 22:28:43 +0200 Subject: Re: pgrouting updated to version 2.2.0-1.pgdg+1 To: Vicky Vergara References: <20160419180107.GC12650@msg.df7cb.de> <5716806D.30603@xs4all.nl> <57169181.5080009@xs4all.nl> Cc: Christoph Berg , PostgreSQL in Debian , Debian GIS Project From: Sebastiaan Couwenberg Message-ID: <571694F9.6040400@xs4all.nl> Date: Tue, 19 Apr 2016 22:28:41 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) X-Mailing-List: pgsql-pkg-debian List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Precedence: bulk Sender: pgsql-pkg-debian-owner@postgresql.org 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 -- Sent via pgsql-pkg-debian mailing list (pgsql-pkg-debian@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-pkg-debian