Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
aurora trees updating for newer locales again
6 views
Skip to first unread message
Axel Hecht
Nov 9, 2012, 11:24:21 AM11/9/12
to
Hi,
there were a few locales for which aurora didn't update on the dashboard,
ach, csb, ff, lij, ms, sw, wo
for Firefox.
Please check your dashboards again.
https://bugzilla.mozilla.org/show_bug.cgi?id=805057 is the bug, and it
was a process mishap during the last merge day, which went undeciphered
for a bit because I was on PTO.
Axel
there were a few locales for which aurora didn't update on the dashboard,
ach, csb, ff, lij, ms, sw, wo
for Firefox.
Please check your dashboards again.
https://bugzilla.mozilla.org/show_bug.cgi?id=805057 is the bug, and it
was a process mishap during the last merge day, which went undeciphered
for a bit because I was on PTO.
Axel
Justin Wood (Callek)
Nov 12, 2012, 12:10:47 AM11/12/12
to Axel Hecht
Axel,
I also saw a similar issue with Locale be. for SeaMonkey
I had CC'ed you on the bug I filed
https://bugzilla.mozilla.org/show_bug.cgi?id=809739
~Justin Wood (Callek)
I also saw a similar issue with Locale be. for SeaMonkey
I had CC'ed you on the bug I filed
https://bugzilla.mozilla.org/show_bug.cgi?id=809739
~Justin Wood (Callek)
Axel Hecht
Nov 12, 2012, 7:34:26 AM11/12/12
to
On 12.11.12 06:10, Justin Wood (Callek) wrote:
> Axel,
> I also saw a similar issue with Locale be. for SeaMonkey
>
> I had CC'ed you on the bug I filed
> https://bugzilla.mozilla.org/show_bug.cgi?id=809739
That's a different issue, actually. The locale didn't have updates for a
> Axel,
> I also saw a similar issue with Locale be. for SeaMonkey
>
> I had CC'ed you on the bug I filed
> https://bugzilla.mozilla.org/show_bug.cgi?id=809739
while, and thus doesn't show up in the queries. If you look at the
versions 1-3 back (don't recall which), you'll see the pushes.
The easiest way to make this pop up for sign-off is to push a dummy
change, possibly to both aurora and beta.
Axel
Justin Wood (Callek)
Nov 12, 2012, 3:48:26 PM11/12/12
to Axel Hecht
Axel Hecht wrote:
> That's a different issue, actually. The locale didn't have updates for a
> while, and thus doesn't show up in the queries. If you look at the
> versions 1-3 back (don't recall which), you'll see the pushes.
>
> The easiest way to make this pop up for sign-off is to push a dummy
> change, possibly to both aurora and beta.
I would love if you could fix the dashboard to always show at least the
> That's a different issue, actually. The locale didn't have updates for a
> while, and thus doesn't show up in the queries. If you look at the
> versions 1-3 back (don't recall which), you'll see the pushes.
>
> The easiest way to make this pop up for sign-off is to push a dummy
> change, possibly to both aurora and beta.
few most recent pushes/compares.
Having to push a change to an l10n teams hg repo, as a product driver is
completely sub-optimal to me.
--
~Justin Wood (Callek)
Axel Hecht
Nov 12, 2012, 5:21:16 PM11/12/12
to
in a world where appversions flow across repos?
There's bug 658656, but that only covers showing more data along the app
as it covers different trees, not spanning trees.
If you could spec this out, that'd be helpful.
Axel
Justin Wood (Callek)
Nov 12, 2012, 11:31:22 PM11/12/12
to Axel Hecht
signoff on it" nomatter if its 1 year old or 1 week old, or 1 minute old.
Such that we are *never* stuck on an old cset just because no-one
requested signoff for a while.
Is that spec enough to give us a way forward?
--
~Justin Wood (Callek)
0 new messages