Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Yucql-0001Fj-8i for bitcoin-development@lists.sourceforge.net; Tue, 19 May 2015 08:26:07 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.45 as permitted sender) client-ip=74.125.82.45; envelope-from=laanwj@gmail.com; helo=mail-wg0-f45.google.com; Received: from mail-wg0-f45.google.com ([74.125.82.45]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Yucqf-0003DR-Sx for bitcoin-development@lists.sourceforge.net; Tue, 19 May 2015 08:26:07 +0000 Received: by wghq2 with SMTP id q2so8700674wgh.1 for ; Tue, 19 May 2015 01:25:55 -0700 (PDT) X-Received: by 10.194.24.70 with SMTP id s6mr52903927wjf.25.1432023955896; Tue, 19 May 2015 01:25:55 -0700 (PDT) Received: from amethyst.visucore.com (dhcp-089-098-016-041.chello.nl. [89.98.16.41]) by mx.google.com with ESMTPSA id t17sm6591215wij.1.2015.05.19.01.25.54 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Tue, 19 May 2015 01:25:55 -0700 (PDT) Date: Tue, 19 May 2015 10:25:57 +0200 From: "Wladimir J. van der Laan" To: bitcoin-development@lists.sourceforge.net Message-ID: <20150519082555.GA17273@amethyst.visucore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) 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 (laanwj[at]gmail.com) -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [74.125.82.45 listed in list.dnswl.org] -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: 1Yucqf-0003DR-Sx Subject: [Bitcoin-development] Bitcoin Core 0.9.5 release candidate 1 tagged 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, 19 May 2015 08:26:07 -0000 Hello, I've just tagged release candidate 1 for 0.9.5 (tag `v0.9.5rc1`). The reason for this backport release is to make BIP66 available on the 0.9 branch. This has been requested by a few users, mostly miners. Full (preliminary) release notes can be found at: https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.md In contrast to 0.10.x releases it is unclear whether there will be enough gitian signatures for a binary release, any help with building is welcome. See https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-process.md (many steps have changed since then, so the release process for 0.10 or master will not work) Wladimir