Sign offs are now open for Lightning 1.0b4.
These will be open until June 7th @ 23:59 PDT.
Note there will be no pre-release like with Thunderbird, if you need
to test your localization please use the nightly l10n builds provided.
Your signoffs are available here:
https://l10n-stage-sj.mozilla.org/shipping/dashboard?av=calendar1.0
If you have any problems, please let us know and we'll make sure
things go fine.
Great job on the 26 locales who are green already, way to go!
Philipp
sq has been green for months now, but I still can't sign off.
Are you aware of the issue?
Besnik
> Great job on the 26 locales who are green already, way to go!
>
> Philipp
> _______________________________________________
> dev-l10n mailing list
> dev-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-l10n
>
>
There are no pushes of yours to the miramar repository, but we'll need
them for the infrastructure to show you something.
Please just make a dummy landing, possibly a white-space change to
something in toolkit, that'll get all your applications there to show
you something to sign off on.
This is something that's really involved to fix on the backend, as it
requires me to teach the beast tricks that it's not built for. Like,
teaching an elephant to walk on 6 legs. First, you gotta get two more
legs on the beast. Working on that, though.
Axel
cs and ru are waiting for bug 577695 to become green.
Any chance to put the filter.py script in work ?
Pavel
Mozilla.cz
filter.py has been put into place, I hope things work without extra
issues.
Triggering new compare-locales results for calendar now.
Axel
Hi Phillip,
I've already signed-off, but I have a late change in a file: should I
open a bug for that or what? The new version is already in the repo.
bye,
Iacopo
I'm not sure how things go, but can't you just request sign-off for a
different revision? Otherwise, maybe I can manually sign off a
revision, which one is it?
I found the problem: I was pushing changes to l10n-mozilla-1.9.2 since I
somehow missed the announcement that we were moving to l10n-miramar. The
revision is not shown on the dashboard yet maybe because I've just
pushed it; anyway there are some changes in the files so is important to
use that for the release. Just in case, this is the revision:
a4f8ace82bca. I'll try to sign it off, but if I can't please make sure
to use that before releasing.
thanks,
Iacopo
P.S. PTW, sorry for the typo on your name on the previous message.
> P.S. PTW, sorry for the typo on your name on the previous message.
No Problem at all, you're not the first and will probably also not be
the last ;-)