| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Translation updates |
| Date: | 2015-11-11 17:01:27 |
| Message-ID: | 56437467.4000206@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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. ;-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-11-11 17:08:21 | Re: pgsql: Generate parallel sequential scan plans in simple cases. |
| Previous Message | Robert Haas | 2015-11-11 15:54:53 | Re: pgsql: Generate parallel sequential scan plans in simple cases. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-11-11 17:08:10 | Python 3 compatibility fun |
| Previous Message | Tom Lane | 2015-11-11 16:31:37 | Re: bootstrap pg_shseclabel in relcache initialization |