This is a tracker bug for releasing Firefox an. Your team's dashboard should be up on http://l10n.mozilla.org/teams/an. The dashboard displays your project's status and helps you (and us) determine what's left to do. Follow it closely to track your Firefox localization progress. You will see this bug listed as part of your dashboard. This helps us to track your project's progress and provide visibilty to your work. The "bugs" here are tracking individual items of work. Some of those will depend on the localization team driving them to completion, while others are for infrastructure that will be handled by Mozilla staff. I'll indicate who is responsible in each bug. We'll also be using two terms for interacting with version control. That's commonly mercurial, or hg, in short. "commit" is used when talking about the actual 'hg commit' command, adding changes to the local version history. "landing" means to commit something and to use 'hg push' to push it from your local version history to the one on hg.mozilla.org, mozilla's server. That's when your changes are public, and make it into the builds mozilla generates, and puts on ftp. If you're unsure what any of the terminology means, feel free to ask. Good places are http://www.mozilla.org/about/forums/#dev-l10n-new-locales or #l10n. Ask in public, you shouldn't assume that you're the only one with the question.
Hi, are we missing anything for starting to have the first Aragonese builds from Mozilla servers?
Hi, we are in a new cycle. Aragonese folks will start working on new string. Can we define any deadline or steps to follow so we can have Aragonese included and enjoy the first builds?
I like the idea of setting a goal. It'll be helpful for orientation (trivia I learned the other day. there was a time when "up" on maps was east, i.e., the orient. Thus Orientation). That goal is for the Aragonese team, there's very little my folks can do to achieve it. As for next steps, http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora-l10n/ has builds, but they don't show up on www.mozilla.org. So filing a bug for that is the next step. Also, the current testers for Aragonese seem to be using language packs, which is great. But we'll want feedback on that aurora build that's out there, too. And of course, fixing the stuff that's put out on the dashboard.
Thanks Pike for the orientations. Should Aragonese team fill that bug? Daniel, in case you didn't know, the dashboard Pike refers is https://l10n.mozilla.org/shipping/dashboard?locale=an
I'm actually talking about https://l10n.mozilla.org/teams/an, which has way more data than the old table.
Thank you both, we're working on it. Pike, we should fill that bug when we fixed the stuff on dashboard, isn't it?
Given that I had to ask how to do that best, I went ahead and filed the bug to get the aurora builds shown on the website. That's parallel to the actual l10n work for Aurora in this cycle. The current mismatch happens every six weeks, so that doesn't block us from anything.
Now it's all up to date at my personal repo http://hg.mozilla.org/users/entaltoaragon_gmail.com/an/ I tried to push changes to aurora-l10n repo http://hg.mozilla.org/releases/l10n/mozilla-aurora/an but I don't have the needed rights to do that.
Hi Daniel, just imported changesets from personal repo into mozilla-aurora/an, no need to merge since we did it recently. Dashboard should update in a few minutes http://hg.mozilla.org/releases/l10n/mozilla-aurora/an
(In reply to Francesco Lodolo [:flod] from comment #9) > Hi Daniel, just imported changesets from personal repo into > mozilla-aurora/an, no need to merge since we did it recently. Dashboard > should update in a few minutes > http://hg.mozilla.org/releases/l10n/mozilla-aurora/an Ciao Francesco, what should be done so Daniel can have rights himself? Should a bug about be opened?
hasn't he got already hg access ? https://bugzilla.mozilla.org/show_bug.cgi?id=741305
(In reply to Pascal Chevrel:pascalc from comment #11) > hasn't he got already hg access ? > https://bugzilla.mozilla.org/show_bug.cgi?id=741305 Oh. He couldn't 'hg push' yesterday. Daniel, were you in a machine with the associated key?
I'm not sure he has access on mozilla-aurora though https://bugzilla.mozilla.org/show_bug.cgi?id=741305#c4 While we fix this, if you have anything to push just ping me or send me an email and I'll be happy to help.
Should we file a new bug to get him access?
(In reply to Toni Hermoso Pulido from comment #12) > (In reply to Pascal Chevrel:pascalc from comment #11) > > hasn't he got already hg access ? > > https://bugzilla.mozilla.org/show_bug.cgi?id=741305 > > Oh. He couldn't 'hg push' yesterday. Daniel, were you in a machine with the > associated key? Yes, I tried it from the same machine from I can push to my user repo. I think that my account hasn't access to push to mozilla-aurora/an repo.
Yes, we should file a bug to beef up the access from level 1 to level 1a (aka scm_l10n).
filed Bug 927373 for scm_l10n commit access
Hey, once we have Aragonese here (https://www.mozilla.org/en-US/firefox/all-aurora.html) —I guess we're still waiting for a weekly push or so—, and apart from keeping green dashboards https://l10n.mozilla.org/shipping/dashboard?locale=an, which are the steps to be followed for popping up in beta and stable list? Just opening more bugs like bug 920669 for beta and stable?
Hi, it seems that aurora strings were not migrated to beta: https://l10n.mozilla.org/teams/an http://hg.mozilla.org/releases/l10n/mozilla-beta/an Should a bug be opened for automating this? Could you guide us a bit about what should be the next steps to follow so Aragonese can have a stable build in just some weeks? Thanks!
Sorry for pestering, any guide?
Axel, what's the next step for us here? Looking at products and web parts, I think it's good for the release channel, isn't it?
Daniel, could you fix Bug 942554, update your Aurora build for the missing 145 strings and do a sign off process for Aurora so as to more things forward? It seeams you never did that. If you don't know how to do the sign off process, I think that Toni can show you. Thanks!
I updated the strings to the Firefox 27 version and fixed that bug at my user repo https://hg.mozilla.org/users/entaltoaragon_gmail.com/an/ Should I push that commits to l10n-aurora repo too?
please do push to the aurora repo directly now that you have access, thanks :)
Pascal, now that's done.
Daniel, you had 145 strings missing yesterday and now you have 1541, maybe our last update deleted some content on your repo? https://l10n.mozilla.org/teams/an
That seems to be, but I'm working with compare-locales and I don't see where the issue is... $ compare-locales ../mozilla-aurora/browser/locales/l10n.ini ../l10n an an: keys: 1187 unchanged: 636 changed: 6969 91% of entries changed Shouldn't the output from compare-locales be the same as dashboard info?
Hi, The same as Daniel. Something happened here (I don't know what). If I checkout last commit and do compare-locales against aurora, everything seems OK. I'm also surprised beta is red. I could have sworn that we managed to get it green from last round.
I did a fake commit and now tip and default tags are pointing to the same head in hg. Aurora build seems OK and translated at dashboard.
cool, could you sign off for Aurora now with this latest commit?
Before the last commit (which I asked Daniel to do): default: http://hg.mozilla.org/releases/l10n/mozilla-aurora/an/rev/c8dc8ac6d0cd tip: http://hg.mozilla.org/releases/l10n/mozilla-aurora/an/rev/24e015008ce6 Running "hg heads" in mozilla-aurora > $ hg heads > changeset: 51:c8dc8ac6d0cd > user: Daniel Martinez <firstname.lastname@example.org> > date: Wed Dec 04 00:15:29 2013 +0100 > summary: Fixed bug #942554 compare-locales: https://l10n.mozilla.org/builds/builders/compare/347841 revision locale: c8dc8ac6d0cd618c136547eb3173232dd4713724 So it was using the same revision. I honestly don't know why the result was completely different.
:flod Thanks for your help about this commit. Comparing previous 'compare' https://l10n.mozilla.org/builds/builders/compare/347841 (from l10n rev 24e015008ce6 that it was tip but not default) with the new one https://l10n.mozilla.org/builds/builders/compare/347844 (from l10n rev 9ad13fa72f87 that now is tip and default), so it seems that 'compares' are done from tip tagged revs.
Hi Daniel, Have you had a chance to sign-off on Aurora yet? Please note that today is the last day to do so. Thanks, Jeff
Hi I think that I can't sign-off because I don't have LDAP account for log in l10n.mozilla.org site. Can you do it for me this time? Should I file a bug requesting an ldap account in order to sign-off in further versions?
(In reply to Daniel Martinez from comment #34) > Hi > > I think that I can't sign-off because I don't have LDAP account for log in > l10n.mozilla.org site. Can you do it for me this time? > > Should I file a bug requesting an ldap account in order to sign-off in > further versions? Hi Daniel, Thanks for the response! Yes, I'll take care of that (just needed your permission) and yes, please file a bug to get an LDAP account so that you can request sign-offs in the future. :-)
Great!, thank you Jeff.
Daniel, as you have hg l10n access, you also have access to the dashboard. Log in with your email address as account, and your ldap password.
Axel, I'm sorry, but I don't have any password for LDAP. How can I set it for my user?
Hi all, Now I have access to l10n dashboard, should I sign-off for Aurora at current version?
Yes, you should sign-off on Aurora the changeset you want to move on to Beta before the end of each cycle.
OK, thanks, now it's done.
We're shipping Aragonese for a while now, let's close this bug. Yay.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.