public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@bitpay.com>
To: xor@freenetproject.org
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
Date: Fri, 13 Jun 2014 16:12:08 -0400	[thread overview]
Message-ID: <CAJHLa0O0mXMJJ3sSD-U+XwJrJUtEtP0Ba0s4==hG9BsSRHR9qg@mail.gmail.com> (raw)
In-Reply-To: <2420822.WsmHDRmLtl@1337h4x0r>

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/



  parent reply	other threads:[~2014-06-13 20:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-13 10:18 [Bitcoin-development] Going to tag 0.9.2 final Wladimir
2014-06-13 11:21 ` Pavel Janík
2014-06-13 11:58   ` Wladimir
2014-06-13 12:02     ` Pavel Janík
2014-06-13 19:24 ` xor
2014-06-13 20:06   ` Matt Whitlock
2014-06-13 20:12   ` Jeff Garzik [this message]
2014-06-14  5:28     ` Wladimir
2014-06-14  5:42       ` Un Ix
2014-06-14  5:49         ` Matt Whitlock
2014-06-14  5:58           ` Un Ix
2014-06-14  6:01             ` Mark Friedenbach
2014-06-14  6:12             ` Wladimir
2014-06-14  6:23         ` Wladimir

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJHLa0O0mXMJJ3sSD-U+XwJrJUtEtP0Ba0s4==hG9BsSRHR9qg@mail.gmail.com' \
    --to=jgarzik@bitpay.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=xor@freenetproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox