Обсуждение: Re: [COMMITTERS] pgsql: Translation updates

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

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

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