Date: Tue, 10 Nov 2015 14:03:41 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [COMMITTERS] pgsql: Translation updates
Message-ID: <20151110170341.GC614468@alvherre.pgsql>
References: <E1ZvoGN-0001Ty-7X@gemulon.postgresql.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <E1ZvoGN-0001Ty-7X@gemulon.postgresql.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

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?  I know it all starts with this
repository,
http://git.postgresql.org/gitweb/?p=pgtranslation/admin.git
and then cp-po-back is used to copy the files from the messages.git repo
to the postgresql.git repo, but it would be better to have more details.
Is there more to it?

(It would also be good to know how to create new branches and how to
destroy one when it goes out of support.)

I would do this by editing this page
https://wiki.postgresql.org/wiki/NLS/admin
and then adding a link to it from
https://wiki.postgresql.org/wiki/Release_process#Before-wrap_tasks
(I decided against doing it myself in case you have different ideas.)

Thanks

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


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