Created attachment 8581623 [details] [diff] [review] yandexDefaultTR As discussed in email. Confidential until this is publicly announced.
Comment on attachment 8581623 [details] [diff] [review] yandexDefaultTR Just making sure: Do we need to add the line browser.search.order.2=Google to mobile/chrome/region.properties so we still have Google as the second option just like the desktop version?
There's no formal requirement to do so. Your call if that's the right thing for your users. Feels like it would be, but I'm not convinced.
Tracking for 37. We're going to take this change on Wed, Mar 25 - the earlier the better.
Comment on attachment 8581623 [details] [diff] [review] yandexDefaultTR Review of attachment 8581623 [details] [diff] [review]: ----------------------------------------------------------------- Mike, we've quickly discussed this among our core team members, and the unanimous decision was to keep Google as an alternative. Could you please update the patch according to this (or should I)?
Ok. (To be clear, it will be an alternative regardless, but this will default it to second place.)
(In reply to Mike Connor [:mconnor] from comment #5) > Ok. (To be clear, it will be an alternative regardless, but this will > default it to second place.) Just to clarify in case there are any doubts: * The list of available searchplugins comes from list.txt * Searchplugins are displayed in alphabetical order (ShortName). This order can be overridden by browser.search.order.* The current patch will display Yandex Google Twitter Wikipedia A patch with "browser.search.order.2 = Google" will currently have the same practical result.
Thanks, Francesco. That was my mistake, then. I've just modified the review flag.
I'm not sure we have clearance to actually land this yet. We should wait for mconnor's OK.
(In reply to Axel Hecht [:Pike] from comment #8) > I'm not sure we have clearance to actually land this yet. We should wait for > mconnor's OK. I don't think either (waiting for confirmation from Yandex that we could put this in public),
I assume this is safe to land? https://blog.mozilla.org/press/2015/03/mozilla-makes-yandex-the-default-search-engine-for-firefox-in-turkey/ Note: don't land directly on l10n-central, but pull changesets from mozilla-aurora into l10n-central (you won't need a merge). I can also do the actual landing if you want.
Yes, please land this ASAP.
ni Ben for comment on how we can most easily incorporate this change in the 37.0 Turkish build.
flod's still landing on l10n/release, and I'll do a sign-off on 37 with the yandex change in the next half-hour.
(In reply to Lawrence Mandel [:lmandel] (use needinfo) from comment #13) > ni Ben for comment on how we can most easily incorporate this change in the > 37.0 Turkish build. Once the change is landed in the turkish mozilla-release l10n repo (http://hg.mozilla.org/releases/l10n/mozilla-release/tr/) I've got to go kick a bunch of stuff by hand.
Also http://hg.mozilla.org/releases/l10n/mozilla-release/tr/rev/b1c55920d4f4 Didn't realize that mozilla-beta was already merged in mozilla-release at this point.
The rebuilds are done now. There's still a couple of verification tests running, but all is looking good AFAICT. Might be a good idea for someone to manually check one of the builds though. Eg: http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/37.0-candidates/build1/mac/tr/Firefox%2037.0.dmg
I've just checked the win32 version and it looked fine to me.
relnoted as "Yandex now default search provider for the Turkish locale"
I think this work is done and the bug can be resolved. Is there any reason to keep it open?
We screwed up the Android bits. The codes are wrong, and wrongly implemented. Sigh. I'll fix that shortly.
This bug is *sort of* fixed in 37. Mike - Can we resolve this as fixed in 37 and file a follow-up to fix the Android bits?
I filed bug 1154759 as a follow up for the Android bits. I'm resolving this as fixed.