[Sugar-devel] Pootle not committing to Git?
walter.bender at gmail.com
Mon Sep 27 08:30:43 EDT 2010
As was pointed out by Chris below, there has been a problem with the
Pootle/git interactions during this release cycle. Not only have
translations not made it into git, but commits to POT files have not
made it into Pootle. (For example,
missing strings that were committed to git  in early August are not
in Pootle.) Have others also observed this problem?
I am not sure what the best path to take so late in the release cycle.
It seems unlikely that even if we got the new POT files committed,
that the translation teams would be able to get their work done soon
enough to meet the release date this week.
I suppose we should: (1) try to figure out what is broken in the
pipeline; and (2) regroup around 0.91?
Meanwhile, should we lift the string freeze? I had been holding off on
a few minor updates in respect for the freeze, but it seems silly not
to start with the latest POT files if we are going to be refreshing
the translation efforts.
On Wed, Sep 22, 2010 at 4:57 PM, Chris Ball <cjb at laptop.org> wrote:
> Looks like Pootle hasn't been pushing changes to Git, see e.g.:
> Does anyone know how to poke it back into action? I need to rebuild a
> bunch of RPMs and activities to add new pt_BR translations.
> Chris Ball <cjb at laptop.org>
> One Laptop Per Child
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
More information about the Sugar-devel