From: Un Ix <slashdevnull@hotmail.com>
To: Matt Whitlock <bip@mattwhitlock.name>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Going to tag 0.9.2 final
Date: Sat, 14 Jun 2014 13:58:39 +0800 [thread overview]
Message-ID: <BLU402-EAS839A956B516EF0EA0D8E42C6140@phx.gbl> (raw)
In-Reply-To: <3528727.dtVK6SVFjZ@crushinator>
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" <bip@mattwhitlock.name> 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.
next prev parent reply other threads:[~2014-06-14 5:58 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
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 [this message]
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=BLU402-EAS839A956B516EF0EA0D8E42C6140@phx.gbl \
--to=slashdevnull@hotmail.com \
--cc=bip@mattwhitlock.name \
--cc=bitcoin-development@lists.sourceforge.net \
/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