From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <bip@mattwhitlock.name>) id 1WvXkZ-0006pd-BY
	for bitcoin-development@lists.sourceforge.net;
	Fri, 13 Jun 2014 20:06:59 +0000
X-ACL-Warn: 
Received: from qmta04.westchester.pa.mail.comcast.net ([76.96.62.40])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1WvXkX-0001dP-KF for bitcoin-development@lists.sourceforge.net;
	Fri, 13 Jun 2014 20:06:59 +0000
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89])
	by qmta04.westchester.pa.mail.comcast.net with comcast
	id Drdz1o0021vXlb854w6sZ4; Fri, 13 Jun 2014 20:06:52 +0000
Received: from crushinator.localnet ([IPv6:2601:6:4800:47f:219:d1ff:fe75:dc2f])
	by omta17.westchester.pa.mail.comcast.net with comcast
	id Dw6r1o00u4VnV2P3dw6sCi; Fri, 13 Jun 2014 20:06:52 +0000
From: Matt Whitlock <bip@mattwhitlock.name>
To: bitcoin-development@lists.sourceforge.net
Date: Fri, 13 Jun 2014 16:06:51 -0400
Message-ID: <2452920.6eTIu8sTlD@crushinator>
User-Agent: KMail/4.13.1 (Linux/3.12.20-gentoo; KDE/4.13.1; x86_64; ; )
In-Reply-To: <2420822.WsmHDRmLtl@1337h4x0r>
References: <CA+s+GJB0ZA0cUSsr=7X8y+YDTUXuXU8x03rX+OZdntwbn-_8TQ@mail.gmail.com>
	<2420822.WsmHDRmLtl@1337h4x0r>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [76.96.62.40 listed in list.dnswl.org]
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WvXkX-0001dP-KF
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 20:06:59 -0000

On Friday, 13 June 2014, at 9:24 pm, xor 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!

Agreed. Does Bitcoin Core not have a release cycle policy? Typically mission-critical projects will enter a code and resource freeze prior to tagging a release candidate, after which point only critical bugfixes are allowed into the release branch. A language translation update does not qualify as a critical bugfix and should be merged during the next release cycle.