Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.169 as permitted sender)
	client-ip=209.85.212.169; envelope-from=laanwj@gmail.com;
	helo=mail-wi0-f169.google.com; 
MIME-Version: 1.0
In-Reply-To: <CA+s+GJDqsFmDhPM=NgLRehokiHBBGdfieDbYUYH4a9ETBCrPPA@mail.gmail.com>
References: <CA+8xBpdLo+VoHiJNJWNn+NPHj9v33=bSXBhkBeoLr73z-qFrBQ@mail.gmail.com>
	<CA+s+GJDqsFmDhPM=NgLRehokiHBBGdfieDbYUYH4a9ETBCrPPA@mail.gmail.com>
Date: Thu, 11 Oct 2012 13:12:15 +0200
Message-ID: <CA+s+GJDiaxn_qOvdmKRKRgQ51QmQ8vfVi4=DAWu+tzTzpmt-Tg@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Post-0.7.1 tree freeze for ultraprune
Precedence: list

On Thu, Oct 11, 2012 at 12:51 PM, Wladimir <laanwj@gmail.com> wrote:
> On Wed, Oct 10, 2012 at 8:40 PM, Jeff Garzik <jgarzik@exmulti.com> wrote:
>> Proposal:  following 0.7.1 release, freeze the tree.  Do not pull
>> anything, until ultraprune is pulled (or rejected, but I think the
>> latter is unlikely).
>
> Yes, I think this is a good idea. Getting ultraprune in should be a priority.
>
> I've just pulled all the small stuff that was already ACKed for
> post-0.7.1, so IMO the freeze can start.

Oops, in my enthusiasm I completely forgot that 0.7.1 is still in rc, not final.

What I merged is:
- #1901 from laanwj/2012_10_remove_strlcpy
- #1900 from Diapolo/optionsmodel_getters
- #1913 from sipa/noi2p
- #1879 from sipa/fdatasync

I don't think any of them is problematic to have in rc2. If it is, we
need to make a branch for 0.7.x at eb49457 and consider master the
0.8.x branch.

Wladimir