From: | Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Road to alpha1 |
Date: | 2009-08-18 01:43:27 |
Message-ID: | 4A8A073F.1000809@timbira.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane escreveu:
> Euler Taveira de Oliveira <euler(at)timbira(dot)com> writes:
>> Peter Eisentraut escreveu:
>>> Possibly, but there aren't going to be any new translations within the
>>> next two days. We may want to reconsider this for the next alpha.
>>>
>> IMHO, it's too much work for an alpha cycle. Why not encourage it _only_ after
>> the last commitfest?
>
> But the translation work is incremental, no? You might waste some
> effort if the same message is changed more than once in a devel cycle,
> but I doubt that's a big problem. Not having to do all the work on a
> tight deadline at the end seems well worth it.
>
I know it is worth doing incremental translation work but I'm talking about
the alpha cycle. We'll need to give time to translators and apply those
modifications. I think it is too much time for an alpha release.
Are you proposing encourage translation without giving time to translate after
the end of commitfest? If so, I think we always give such a choice ('cause the
translations are in PGFoundry); we just need some committer to grab those
modifications and apply to CVS. +1 to add this step to alpha release process.
--
Euler Taveira de Oliveira
http://www.timbira.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-08-18 04:44:33 | Re: [PATCH] plpythonu datatype conversion improvements |
Previous Message | Pierre Frédéric Caillaud | 2009-08-18 01:27:20 | Re: COPY speedup |