public inbox for [email protected]  

help / color / mirror / Atom feed

From: Alvaro Herrera <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: [email protected]
Subject: Re: [COMMITTERS] pgsql: Translation updates
Date: Wed, 11 Nov 2015 16:05:25 -0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-hackers>

Peter Eisentraut wrote:
> On 11/10/15 12:03 PM, Alvaro Herrera wrote:
> > Peter Eisentraut wrote:
> >> Translation updates
> >>
> >> Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git
> >> Source-Git-Hash: cd263526676705b4a8a3a708c9842461c4a2bcc3
> > 
> > Hi Peter,
> > 
> > Would you please document this process?
> 
> It's documented in src/tools/RELEASE_CHANGES (except I don't do the
> tagging anymore).  You can try it yourself.

Ah, that's it, thanks.  I remember doing it once in the past and
couldn't remember where had I gotten the procedure from.  I guess I will
add a pointer to that file in the recently created Release Process wiki
page.

> > (It would also be good to know how to create new branches and how to
> > destroy one when it goes out of support.)
> 
> Yeah that one's a bit trickier and potentially confusing.  See recent
> discussion about branch naming on the translators list.  I usually just
> check the commit history for how it was done the previous time. ;-)

Aha.  (I should get a fresh clone of that repository, I guess. I
probably have extra branches now.)

BTW I'm confused about the message-branches.txt file.  Aren't we
supposed to have an entry for REL9_5_STABLE in there?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

view thread (102+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: [COMMITTERS] pgsql: Translation updates
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox