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 ) id 1WvhaH-0008Al-E9 for bitcoin-development@lists.sourceforge.net; Sat, 14 Jun 2014 06:37:01 +0000 Received: from mail-yk0-f173.google.com ([209.85.160.173]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WvhaF-00032J-Pj for bitcoin-development@lists.sourceforge.net; Sat, 14 Jun 2014 06:37:01 +0000 Received: by mail-yk0-f173.google.com with SMTP id q200so2739013ykb.4 for ; Fri, 13 Jun 2014 23:36:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=j9jUw3YWWVxZwVK4I3UzpagvbmyBWK0fNjS82Ez6vrU=; b=g07KyF0ShkRETcChx2EZ5jvuUDamwpyH2iBAwOx2qaxz5CkmrZ9F6oR+OWT3NCdi6k PoDMj/kT3ErzlphohmZc9Vtn5EPNhOjH4RaLfGuwCciPOKRBVaKe5hQaC8T042syZuQD yCVAiVDAlaMiJ1ffhuWOMkaxomsiB06Y8RQnzDebBsMYmHPTriMiayNWWulKdq4FnYZu LR/SNNhNqEKV579/RvUmTYLsCLNKKEmAsu182zcDWVi2zFwadJmmigacZT+eykHa/twr d0Wa2du89lsFp3paYbjg0Id1scXXi5/MJSv/CyycUasHDg7F/0dQ13Ifko/pVQdJo33o Vw0Q== X-Gm-Message-State: ALoCoQmYCv5SVOIl+phaFv9a9KWAYV72rSG2pZo0cEjxVBIGy1JTJ8dCq2UjZPdcLxZ/D679rZbz X-Received: by 10.236.160.130 with SMTP id u2mr24215yhk.161.1402726106410; Fri, 13 Jun 2014 23:08:26 -0700 (PDT) Received: from [192.168.127.212] (50-0-36-179.dsl.dynamic.sonic.net. [50.0.36.179]) by mx.google.com with ESMTPSA id t5sm9877973yhd.6.2014.06.13.23.08.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Jun 2014 23:08:25 -0700 (PDT) Message-ID: <539BE538.9070807@monetize.io> Date: Fri, 13 Jun 2014 23:01:28 -0700 From: Mark Friedenbach Organization: Monetize.io Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <3528727.dtVK6SVFjZ@crushinator> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1WvhaF-00032J-Pj 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jun 2014 06:37:01 -0000 Not when failure is defined as, e.g., extra text pushing a UI element down such that the button the user needs to click is no longer visible. You don't test that except by having a human being run through some example workflows, which is presumably happening during the release process. On 06/13/2014 10:58 PM, Un Ix wrote: > Was joking, but isn't the translation process back-ended with runtime > tests to ensure that any stray chars etc cause the application to > fail? > >> On 14/06/2014, at 1:49 pm, "Matt Whitlock" >> wrote: >> >>> On Saturday, 14 June 2014, at 1:42 pm, Un Ix wrote: How about a >>> prize for anyone who can spot any "malicious" strings within next >>> hour? >> >> I think it's more an issue of accidental breakage than any >> maliciousness. One character in the wrong place in a language >> bundle somewhere can make the difference between success and >> runtime failure, and it may not be immediately apparent when >> running in unaffected locales. This kind of problem isn't likely to >> result in data loss (or money loss, where money is data, is in >> Bitcoin), but it could be enough to necessitate scrapping the whole >> release, which would look bad and prompt users to question the dev >> team's quality control process. >