Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.53 as permitted sender)
	client-ip=74.125.82.53; envelope-from=laanwj@gmail.com;
	helo=mail-wg0-f53.google.com; 
MIME-Version: 1.0
In-Reply-To: <CA+8xBpdLo+VoHiJNJWNn+NPHj9v33=bSXBhkBeoLr73z-qFrBQ@mail.gmail.com>
References: <CA+8xBpdLo+VoHiJNJWNn+NPHj9v33=bSXBhkBeoLr73z-qFrBQ@mail.gmail.com>
Date: Thu, 11 Oct 2012 12:51:55 +0200
Message-ID: <CA+s+GJDqsFmDhPM=NgLRehokiHBBGdfieDbYUYH4a9ETBCrPPA@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 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.

Wladimir