Subject: Re: [COMMITTERS] pgsql: Translation updates
To: Alvaro Herrera <alvherre@2ndquadrant.com>
References: <E1ZvoGN-0001Ty-7X@gemulon.postgresql.org>
 <20151110170341.GC614468@alvherre.pgsql>
Cc: pgsql-hackers@postgresql.org
From: Peter Eisentraut <peter_e@gmx.net>
Message-ID: <56437467.4000206@gmx.net>
Date: Wed, 11 Nov 2015 12:01:27 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
 Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151110170341.GC614468@alvherre.pgsql>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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.

> (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. ;-)


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