Den 23-09-2011 03:29, Colin Walters skrev:
Many translations in clutter for "default:LTR" are broken; this causes a
warning at startup.
http://git.gnome.org/browse/clutter/tree/clutter/clutter-main.c#n485
Here's what seems to be affected:
po/da.po:msgid "default:LTR"
po/da.po-msgstr ""
po/kn.p
On Thu, Sep 22, 2011 at 10:44:32PM +0100, Bastien Nocera wrote:
> I think that, at the very least for GNOME 3.4 onwards, we should switch
> to using a keyword in bugzilla, and the release-team, docs team and i18n
> teams can monitor newly request breaks, through RSS feeds (the design
> team does th
Den 23-09-2011 09:30, Kenneth Nielsen skrev:
Den 23-09-2011 03:29, Colin Walters skrev:
Many translations in clutter for "default:LTR" are broken; this causes a
warning at startup.
http://git.gnome.org/browse/clutter/tree/clutter/clutter-main.c#n485
Here's what seems to be affected:
po/da.po:
On Fri, Sep 23, 2011 at 9:40 AM, Olav Vitters wrote:
> On Thu, Sep 22, 2011 at 10:44:32PM +0100, Bastien Nocera wrote:
>> I think that, at the very least for GNOME 3.4 onwards, we should switch
>> to using a keyword in bugzilla, and the release-team, docs team and i18n
>> teams can monitor newly r
On Fri, Sep 23, 2011 at 09:53, Baptiste Mille-Mathias
wrote:
> On Fri, Sep 23, 2011 at 9:40 AM, Olav Vitters wrote:
>> On Thu, Sep 22, 2011 at 10:44:32PM +0100, Bastien Nocera wrote:
>>> I think that, at the very least for GNOME 3.4 onwards, we should switch
>>> to using a keyword in bugzilla, an
On Fri, Sep 23, 2011 at 10:11:13AM +0200, Jorge González wrote:
> There could be a shared calendar. I have my own to know when we
> release and when are we in string freeze and such. It's very easy.
http://www.gnome.org/start/unstable/schedule.ics
webcal://www.gnome.org/start/unstable/schedule.ics
Op Vr, 2011-09-23 om 10:11 +0200 skryf Jorge González:
> On Fri, Sep 23, 2011 at 09:53, Baptiste Mille-Mathias
> wrote:
> > On Fri, Sep 23, 2011 at 9:40 AM, Olav Vitters wrote:
> >> On Thu, Sep 22, 2011 at 10:44:32PM +0100, Bastien Nocera wrote:
...
> > As Bastien reported it is also hard to k
On 23 September 2011 08:40, Olav Vitters wrote:
> The Bugzilla way of doing this is to use flags. A flag is either defined
> for attachments _or_ (not and) bugs. This is possible on our currently
> bugzilla; we just do not use them.
For what it's worth this is exactly what we do in MeeGo for
dist
On Fri, Sep 23, 2011 at 09:57:15AM +0100, Ross Burton wrote:
> On 23 September 2011 08:40, Olav Vitters wrote:
> > The Bugzilla way of doing this is to use flags. A flag is either defined
> > for attachments _or_ (not and) bugs. This is possible on our currently
> > bugzilla; we just do not use th
On 23 September 2011 10:58, Olav Vitters wrote:
>> For what it's worth this is exactly what we do in MeeGo for
>> distribution freezes and we find it works very well.
>
> Do you have multiple freezes? Do you use one flag or multiple? How do
> you handle multiple teams and e.g. one flag?
We have a
Am 22.09.2011 22:02, schrieb Zoltan Kota:
> Hi,
>
> I plan to push a new release of pybliographer next week. Please, check
> your translations!
> Thanks!
>
> Zoltan
> ___
> gnome-i18n mailing list
> gnome-i18n@gnome.org
> http://mail.gnome.org/mailman/l
On Thu, 2011-09-22 at 22:02 +0200, Zoltan Kota wrote:
> I plan to push a new release of pybliographer next week. Please, check
> your translations!
I've checked your strings instead, and filed
https://sourceforge.net/tracker/?func=detail&aid=3413277&group_id=4825&atid=104825
about missing plural h
On Fri, 2011-09-23 at 09:40 +0200, Olav Vitters wrote:
> On Thu, Sep 22, 2011 at 10:44:32PM +0100, Bastien Nocera wrote:
> > I think that, at the very least for GNOME 3.4 onwards, we should switch
> > to using a keyword in bugzilla, and the release-team, docs team and i18n
> > teams can monitor new
On Fri, Sep 23, 2011 at 12:51:04PM +0100, Bastien Nocera wrote:
> Here's the workflow with a keyword:
> 1. Developer adds a patch to an important bug, and realises that the
> patch needs to make it to stable during a freeze (possibly through a
> banner, auto-updated via ical)
> 2. Developer adds "f
On 09/23/2011 07:58 AM, Olav Vitters wrote:
> I think that will add too much burden on the people who have to approve?
>
> I don't track RSS at all. Release-team gets a lot of freeze breaks and I
> want to be notified immediately, not after a delay. I need to see the
> comments that other teams ma
On Thu, 2011-09-22 at 21:24 -0400, Shaun McCance wrote:
> On Thu, 2011-09-22 at 22:44 +0100, Bastien Nocera wrote:
> > I think that, at the very least for GNOME 3.4 onwards, we should switch
> > to using a keyword in bugzilla, and the release-team, docs team and i18n
> > teams can monitor newly req
On Fri, 2011-09-23 at 07:43 +0100, Emmanuele Bassi wrote:
>
> On 23 September 2011 02:29, Colin Walters wrote:
> > Many translations in clutter for "default:LTR" are broken; this causes a
> > warning at startup.
> >
>
> to the translators: this works exactly like the identical string in gtk+:
>
Hi!
> Instead of keywords, we could just add bugzilla pseudo accounts for
> "string-freeze-br...@gnome.bugs", "ui-freeze-br...@gnome.bugs",
> "code-freeze-br...@gnome.bugs". Then to request a break, just cc: the
> appropriate address on the bug along with a comment explaining why.
> Release/docs/i
18 matches
Mail list logo