Re: Preparation for PostgreSQL releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20

Поиск
Список
Период
Сортировка
От Guillaume Lelarge
Тема Re: Preparation for PostgreSQL releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20
Дата
Msg-id 46E799F8.5070206@lelarge.info
обсуждение исходный текст
Ответ на Re: Preparation for PostgreSQL releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20  (Dave Page <dpage@postgresql.org>)
Список pgsql-hackers
Dave Page a écrit :
> Guillaume Lelarge wrote:
>> Tom Lane a écrit :
>>> Bruce Momjian <bruce@momjian.us> writes:
>>>> Alvaro Herrera wrote:
>>>>> Does this mean that if I commit something in these days to those
>>>>> branches, it will not show up in the releases?
>>>> It certainly will show up if you do it before the packagers pull their
>>>> CVS copies.
>>> No, it will show up if you do it before Marc "cvs tag"s the release.
>>> Which I am currently thinking shouldn't happen till Friday or so.
>>>
>>
>> Is it Marc's job to sync the translation on PostgreSQL CVS with those
>> from the pgtranslation project ? I remember this is a part of the build
>> process but I don't know who does this.
> 
> No, thats Peter.
> 
> I'm not sure if he usually does it for point releases though.
> 

I hope he already did it for minor releases. If not, I wonder why
pgtranslation project has major branches.

I really need to see this happening at least on these minor releases. I
worked a lot on the .po files from 7.4, 8.0, 8.1 and 8.2, fixing some
translation's issues, "fine-tuning" the translations. Why isn't there
some kind of automatic process that sync the translations, once per
month for example ? if this can be done, I can work on this.


-- 
Guillaume.
http://www.postgresqlfr.org/
http://dalibo.com/


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Dave Page
Дата:
Сообщение: Re: Preparation for PostgreSQL releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20
Следующее
От: Stefan Kaltenbrunner
Дата:
Сообщение: Re: pgcrypto related backend crash on solaris 10/x86_64