709128 - (fx-l10n-ff) [ff] Firefox release tracker Fulah

Status: RESOLVED FIXED

(Mozilla Localizations :: ff / Fulah, defect)

Description

[Axel Hecht [:Pike]]

This is a tracker bug for releasing Firefox ff.

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]]

This is based on the registration bug 686891.

Comment 2

[Axel Hecht [:Pike]]

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

I hope to get builds RSN, too.

Noteworthy, for getting the current status in good shape for this cycle, you can make significant headway with `hg mv` and `hg cp` of the files that go into devtools.

If you need help with that, drop a note.

Also, now that we've got a repo up, you, Ibrahima, and Dwayne should set up a plan on who's going to push to the repos.

Comment 3

[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 4

[Ibrahima SARR]

Hi, I have translated more than 82% of Firefox but the dashboard only show 68% and "pending" status! This has been unchanged for a month. When can we expect to see things moving?
Best regards abd Happy New Year!

Comment 5

[Milos Dinic [:Milos]]

Axel, mind taking a look at this?

Comment 6

[Axel Hecht [:Pike]]

Dwayne landed your work on aurora on the 18th, and now we're green. There was still a pending sign-off on a state with missing strings, so I rejected that.

Milos, can you make sure that the review comments from the registration bug are addressed?

Comment 7

[Ibrahima SARR]

Hi,
I am quite frustrated thing have not evolved since even though I completed my translation, those available on Pootle (Locamotion). I have no control over anything else so I just wait and hope things will happen. Fulah status has not evolved much since November and I have not been able to get in touch with Dwayne, who is probable quite busy.

Comment 8

[Axel Hecht [:Pike]]

Hi Ibrahima, sorry that this doesn't feel smooth.

We're very happy that we have people like Dwayne that allow the Mozilla community to help new localizations on board. On the other hand, if someone like Dwayne runs into some issues with her or his personal availability, that has a serious impact. Which in fact isn't any different if that person is a volunteer or paid staff. At this point, there's nothing concrete I can help you with, sorry.

I'm hoping to get some updates by end of next week.

Comment 9

[Milos Dinic [:Milos]]

(In reply to Axel Hecht [:Pike] from comment #6)
> Milos, can you make sure that the review comments from the registration bug
> are addressed?

Review comments in registration bug are addressed, all but one, which is

[intl.accept_languages=ff-ff, fuc, fr-fr, fr] which should be [intl.accept_languages=ff, fr] in toolkit/chrome/global/intl.properties.

Comment 10

[Ibrahima SARR]

Corrected in Pootle.

Comment 11

[Dwayne Bailey]

(In reply to Milos Dinic [:Milos] from comment #9)
> (In reply to Axel Hecht [:Pike] from comment #6)
> > Milos, can you make sure that the review comments from the registration bug
> > are addressed?
> 
> Review comments in registration bug are addressed, all but one, which is
> 
> [intl.accept_languages=ff-ff, fuc, fr-fr, fr] which should be
> [intl.accept_languages=ff, fr] in toolkit/chrome/global/intl.properties.

Fixed in 06bf3251da3a

Comment 12

[Milos Dinic [:Milos]]

(In reply to Dwayne Bailey from comment #11)
> (In reply to Milos Dinic [:Milos] from comment #9)
> > (In reply to Axel Hecht [:Pike] from comment #6)
> > > Milos, can you make sure that the review comments from the registration bug
> > > are addressed?
> > 
> > Review comments in registration bug are addressed, all but one, which is
> > 
> > [intl.accept_languages=ff-ff, fuc, fr-fr, fr] which should be
> > [intl.accept_languages=ff, fr] in toolkit/chrome/global/intl.properties.
> 
> Fixed in 06bf3251da3a

Looks good, thanks Dwayne.

Comment 13

[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 Fulah 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 Fulah. You can check the status of your latest builds and some team info on l10n dashboard teams page at https://l10n.mozilla.org/teams/ff . As the website evolved, you should 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.

== 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!