Re: Translations not used in Evolution (was Re: Evolution and Evolution-Data-Server branched)

On Mon, 2005-09-19 at 13:00 +0200, Vincent Untz wrote:
> On Mon, September 19, 2005 10:24, Harish Krishnaswamy wrote:
> >    However, it would be helpful if you could make incremental updates
> > during the development cycle [2]  or have all your huge changes
> > committed at least a day prior to the deadline. This would limit the
> > damage caused by errors in packaging or missing commits.
> While I agree that your first solution would be nice, some translators
> don't do this because it's really hard to keep translating the modules
> when there's no string freeze. So they only translate when string
> freeze is here.
Sounds reasonable.

> I suggest you release the module on the Monday of the release (as
> requested by the release team). 
Yes. I have been doing so - it is to adhere to this deadline that I
need to cut-off commits much earlier to allow testing and QA
verification [Yes, we now have an array of written test cases and a
dedicated team that runs them, regresses fixes etc. for nearly a full
day :-)]
> Translators know that if they
> commit their translations on Monday, it might already be too late
> for their translations to go in the release. But if you need to
> make the tarball for the release before Monday, then send an e-mail
> to gnome-i18n so translators know that the tarball will be made
> before Monday.
This sounds fine. It is almost always the Friday before the due-date,
but I can post a heads-up to gnome-i18n in future.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]