From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QdvLE-0002LD-Bv for bitcoin-development@lists.sourceforge.net; Tue, 05 Jul 2011 02:26:24 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.83.175 as permitted sender) client-ip=74.125.83.175; envelope-from=gavinandresen@gmail.com; helo=mail-pv0-f175.google.com; Received: from mail-pv0-f175.google.com ([74.125.83.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1QdvLD-00050G-7x for bitcoin-development@lists.sourceforge.net; Tue, 05 Jul 2011 02:26:24 +0000 Received: by pvf24 with SMTP id 24so6912344pvf.34 for ; Mon, 04 Jul 2011 19:26:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.255.7 with SMTP id c7mr3086902wfi.410.1309832777200; Mon, 04 Jul 2011 19:26:17 -0700 (PDT) Received: by 10.142.185.13 with HTTP; Mon, 4 Jul 2011 19:26:17 -0700 (PDT) In-Reply-To: <1309828239.29355.28.camel@Desktop666> References: <1309801974.3423.80.camel@Desktop666> <1309811972.29355.19.camel@Desktop666> <1309828239.29355.28.camel@Desktop666> Date: Mon, 4 Jul 2011 22:26:17 -0400 Message-ID: From: Gavin Andresen To: Matt Corallo Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 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: 1QdvLD-00050G-7x Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Encrypted Wallet Backward Compatibility 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: Tue, 05 Jul 2011 02:26:24 -0000 > Despite this being quick, I really want to get 0.3.24 out and rolling so > that we have us much lead time on 0.4 as possible Agreed. > All that needs to happen for that is to agree on either > https://github.com/bitcoin/bitcoin/pull/378 or > https://github.com/bitcoin/bitcoin/pull/381' I don't think 0.3.24 "needs" either of those pulls. Fixing downgrade-to-0.3.24 is low on the priority list, because downgrade-to-something-before-0.3.24 is just about as likely, and that has to do something mostly reasonable. I just pulled https://github.com/bitcoin/bitcoin/pull/379 "Do not use comma as thousands separator", and pulled a block-chain lock-in at block 13444. Those were the only issues I think really need to be in 0.3.24. -- -- Gavin Andresen