711107 - (fx-l10n-lij) [lij] Firefox release tracker Ligurian

Status: VERIFIED FIXED

(Mozilla Localizations :: lij / Ligurian, defect)

Description

[Axel Hecht [:Pike]]

This is a tracker bug for releasing Firefox lij.

This bug is not that detailed, but as we get particular work items, they should
block this bug for tracking and discoverability.

The "bugs" here are tracking indiviual items of work. Some of those will depend on the localization team to be driven to completion, others are for infrastructure that will be handled by staff. I'll indicate which in the individual bugs.

Comment 1

[Axel Hecht [:Pike]]

The dashboard is now up, at https://l10n-stage-sj.mozilla.org/shipping/dashboard?locale=lij.

I hope to get builds RSN, too.

I'd still like you guys to make a bit more headway in terms of the translation coverage, too.

Also, now that we've got a repo up, you, Alessio, you probably want to file a bug to get hg commit access so that you can update the localization yourself. Details on the process details for that are at https://wiki.mozilla.org/L10n:Becoming_an_Official_Localization#hg_write_access

Comment 2

[alessio]

Well! Thanks, I hope we have the 85% coverage in the next month.
I've opened the [Bug 711347] for hg access.
So this bug can be closed?

Comment 3

[Axel Hecht [:Pike]]

We'll keep this bug open until we have shipped a Ligurian version and it's out of beta. What's needed to get there is tracked in the bugs "blocking" this one. "Blocking" is jargon, and usually, a bug cannot be closed before all bugs are closed that this one is blocked on, or "depends".

Comment 4

[Axel Hecht [:Pike]]

Hi, just a quick update.

We're still waiting for the actual builds, coop said he landed those today, so tomorrow we should get builds.

Sadly, the setup of our infrastructure took longer than usual, and we're not all set up, and Firefox 10 moved to Beta earlier today.

To give us a proper timing, and to make things less complicated technically, we'll want to move your work onto the Firefox 11 train.

One thing that came in with 11 is another rename of two files. If we can help with those, please follow up here.

Beyond that, we're hoping to see you get into good shape to land and test really soon now.

Thanks. Axel

Comment 5

[alessio]

Hi, a quick information.
Like I've said we have now the 85% of translation coverage :)

Comment 6

[alessio]

Hi,
We have translated all that can be translate on Firefox Aurora...
On Signoffs page we have 91%
https://l10n-stage-sj.mozilla.org/shipping/dashboard?locale=lij

Comment 7

[alessio]

Hi! I've seen that the version 10 has come out..
So we have somewhere a Beta version of Ligurian Firefox 10? and if so, where it is?

Comment 8

[alessio]

Sorry I want say the beta 11...

Comment 9

[alessio]

Now there is not Bug blocking this, so the Ligurian can be shipped to the 11 Final version? Or I must do another actions to permit this? thanks

Comment 10

[Axel Hecht [:Pike]]

I just had a quick test, and found two issues. Filed the bugs, too.

Comment 11

[alessio]

Problem if I try to go to url:
www.mozilla.org/lij/firefox/fx/

it redirect me to beta channel:
http://www.mozilla.org/lij/firefox/beta/

Comment 12

[Milos Dinic [:Milos]]

Firstly, congratulations team!

You have worked and managed to get all the dependencies for this bug fixed, which means that productization for Ligurian Firefox is all done. Please take a minute or two and read the next steps to follow.

== Aurora ==

Every 6 weeks, we will update aurora repositories with new strings that will require some additional time spent on it. As you probably already know, we advise all localizers to use Aurora channel for all translations, so that we can merge them with Beta channel when needed without any regressions. So, please use Aurora as your primary working repo, and in case you're landing a fix to Beta channel, please port it back to Aurora too. Once the Aurora builds are available, please use them as much as you can for the purpose of testing your own translations and making sure everything is as it should be.

== Bugs ==

Please check your dashboards every now and then to see if there are some bugs filed against Firefox in Ligurian. You can check the status of your latest builds and some team info on l10n dashboard teams page at https://l10n-stage-sj.mozilla.org/teams/lij . As the website evolves, you'll start using that as your primary source of info related to localization.

One other important thing to have in mind is webdashboard. We use webdashboard to show contributors bugs related to web localization for their locale. This is really important as we use our websites to promote localized Firefox builds. Web dashboard can be found at http://l10n.mozilla-community.org/webdashboard/?locale=lij .

== Staying connected ==

You should also follow the Mozilla l10n newsgroup, http://www.mozilla.org/community/forums/#dev-l10n, available as mailing list, newsgroup or google group. The traffic isn't too high frequency. 

You'll find all announcements at http://www.mozilla.org/community/forums/#dev-l10n-announce . Those are vital to read, as they include things that the l10n-drivers want you to know and attend to. 

There's a third group, http://www.mozilla.org/community/forums/#dev-l10n-web, where we discuss web localization issues. That's a separate group as quite a few localization teams have dedicated volunteers for that.

Another important thing is staying in touch with community and make yourself available for anyone who wants to contribute. So, if possible, get in touch with community on community forums, get feedback and possibly more volunteers.

Enjoy and congratulations!

Comment 13

[alessio]

Thanks: the last question-> Where can I find the new Aurora Strings?

Comment 14

[Milos Dinic [:Milos]]

So, you copy them over from hg.mozilla.org/releases/mozilla-aurora

and you know you have missing strings either by using dashboard or compare-locales python script.