Path: g2news2.google.com!news2.google.com!Xl.tags.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!nntp.mozilla.org!news.mozilla.org.POSTED!not-for-mail
NNTP-Posting-Date: Wed, 16 Mar 2011 11:30:28 -0500
Message-ID: <4D80E5A4.4000601@mozilla.com>
Date: Wed, 16 Mar 2011 12:30:28 -0400
From: Ben Hearsum <bhear...@mozilla.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b13pre) Gecko/20110314 Thunderbird/3.3a3pre
MIME-Version: 1.0
Newsgroups: mozilla.dev.planning
To: Gervase Markham <g...@mozilla.org>
Subject: Re: Firefox 4 Final Release Schedule
References: <mailman.1727.1300211507.4383.dev-planning@lists.mozilla.org> <cs-dnZDuvcHwMeLQnZ2dnUVZ_smdnZ2d@mozilla.org> <mailman.1736.1300214581.4383.dev-planning@lists.mozilla.org> <tomdnQTrFb5oKOLQnZ2dnUVZ_tWdnZ2d@mozilla.org> <u_Wdnd65AsB8fB3QnZ2dnUVZ_v-dnZ2d@mozilla.org> <4D80E30A.10108@mozilla.com> <aM6dnVx75rOPeR3QnZ2dnUVZ_jGdnZ2d@mozilla.org>
In-Reply-To: <aM6dnVx75rOPeR3QnZ2dnUVZ_jGdnZ2d@mozilla.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 30
X-Usenet-Provider: http://www.giganews.com
NNTP-Posting-Host: 24.246.74.78
X-AuthenticatedUsername: NoAuthUser
X-Trace: sv3-j23XUU4kQzK7gqGd1BAlKHlDDrgcW3OGqY6w5UdlQ/OgqffGzkgRT5usM99qDDdLC0RLRYT6H6bm4SQ!d1Dvb//cJYR+Nl35u7y+4lYX9JqSfD4yug+dpRmHVqIRf0CRa7jH5V+vtkldVeaKlQ==
X-Complaints-To: abuse@mozilla.org
X-DMCA-Complaints-To: ab...@mozilla.org
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 2920

On 03/16/11 12:23 PM, Gervase Markham wrote:
> On 16/03/11 16:19, Ben Hearsum wrote:
>> I don't think a final release is the place for us to be doing manual,
>> error prone hackery like this. I'm strongly against doing this.
> I'm not saying we need to rush to do it in time for the release on March
> 22nd - we can take our time, and get the .vi community to test it for
> us. We could even release it as "beta" language, as I believe we have
> done for some languages in previous releases - a separate section at the
> bottom of the download page.
>
> I'm just saying that for 1.32% of the world/500K ADUs, however you want
> to put it, plus the big efforts of the .vi l0n team, we should be able
> to do _something_ more than just say "sorry, guys, your l10n team was a
> day late so now you have to wait for Firefox 5".
>
> Gerv

I didn't say we had to wait until 5. Adding it in 4.0.1 is perfectly 
fine with me.

I'm against doing it in 4.0 because we have no experience adding a 
locale at this point in a release, from a RelEng standpoint. We have no 
ideas what the gotchas are, or what things it will cause issue with in 
subsequent point releases. A final release is tricky and complicated 
enough without adding in this unknown.

We are working on making late-stage locale additions possible, but 
currently, it's not.

- Ben