Just a reminder about the l10n policy on the
browser.search.siteSearchURL pref in region.properties introduced in bug
https://bugzilla.mozilla.org/show_bug.cgi?id=482229. Also, at the end of
the e-mail I'm announcing a mass-landing on Saturday morning for locales
that won't change siteSearchURL by then.

REMINDER:

As we're approaching the opt-ins for beta4, it would be great if you
could land this string according to the following policy as soon as
possible for you. *No review is required for this landing.*

The policy:

1. If the default search provider is not Google, then use their site
specific search. Site specific search feature is now a requirement for a
search engine to become a default in a locale. [1]

2. If the default search provider is Google, then:

    2.1. Use
http://www.google.com/search?ie=UTF-8&oe=UTF-8&sourceid=navclient&q=s...{moz:domain}+{searchTerms}
(without the hard-coded locale code) and let Google do the language
detection.

    2.2 If the language detection by Google is not satisfactory, use an
empty value for now to disable the pref and file a bug to investigate.
An empty value to disable the pref should look like this:
browser.search.siteSearchURL=
The bug should be filed in Mozilla Localizations > {your locale}. Please
CC s...@mozilla.com.

[1] Currently the only case here is Russian, I filed a bug for it:
https://bugzilla.mozilla.org/show_bug.cgi?id=485974

As noted previously, we're making an exception from the "no changes to
region.properties without review" rule for this single situation. Please
land the browser.search.siteSearchURL pref according to the above policy
on l10n-central and l10n-mozilla-1.9.1 in your locale. *No review is
required for this landing.* However, please only change this single pref
in your landings, so that we can refer to it easily later.

MASS-LANDING:

For the locales that won't land this on their own, I'm going to do a
mass-landing this Saturday at 10 AM UTC. I will use
http://www.google.com/search?ie=UTF-8&oe=UTF-8&sourceid=navclient&q=s...{moz:domain}+{searchTerms}
if the pref is missing from region.properties or if its value is
different from the values outlined in the policy. If that doesn't work
too well for your locale, please file a bug and CC me on it.

I hope this will make the opting-in process easier, but if you don't
feel so, feedback is obviously welcome.

So if your locale is already green on 1.9.1, you can either just wait
until Saturday for my landing and then opt in, or land the string
yourself and opt in earlier (well, that actually depends on when Axel
will start the opt-in thread :)

If your locale is red, just remember to |hg pull -u| on Saturday. If
you're green, do that too, please.

I'll be posting in the next days about this again. Comments welcome.

Thanks and best of luck!
Staś

Just to add to what I posted yesterday: if you want to land
siteSearchURL yourself, please do so. Just be sure to follow the policy
outlined in my previous post in this thread.

I'll be doing the mass-landing tomorrow (Saturday) at 10 AM UTC to make
sure all locales have this string. But this doesn't mean you can't land
it yourself before. If you do, it's going to be even easier for me, so
please don't be shy ;)

Sorry if I wasn't clear in my first message.

Best,
Staś

During the next hour or so I will be doing the landings. Please remember
to |hg pull -u| the next time you're working in your clone.

Thanks,
Staś

--Staś