Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 74.125.82.173 as permitted sender)
	client-ip=74.125.82.173; envelope-from=jgarzik@bitpay.com;
	helo=mail-we0-f173.google.com; 
MIME-Version: 1.0
In-Reply-To: <2420822.WsmHDRmLtl@1337h4x0r>
References: <CA+s+GJB0ZA0cUSsr=7X8y+YDTUXuXU8x03rX+OZdntwbn-_8TQ@mail.gmail.com>
	<2420822.WsmHDRmLtl@1337h4x0r>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 13 Jun 2014 16:12:08 -0400
Message-ID: <CAJHLa0O0mXMJJ3sSD-U+XwJrJUtEtP0Ba0s4==hG9BsSRHR9qg@mail.gmail.com>
To: xor@freenetproject.org
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
Precedence: list

On Fri, Jun 13, 2014 at 3:24 PM, xor <xor@freenetproject.org> wrote:
> On Friday, June 13, 2014 12:18:37 PM Wladimir wrote:
>> If I do not hear anything, I will do a
>> last-minute language import
>
> High risk projects as Bitcoin should NOT see ANY changes between release
> candidates and releases.
>
> You can cause severe havoc with ANY changes. Humans make mistakes!
> Please do not do such things!

As a general principle, I agree.  Other projects have translation
freeze points to address this.  Although it is a small holistic risk,
in theory, someone could maliciously change strings at the last minute
in a language maintainers don't know well.

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/