[Bitcoin-development] Post-0.7.1 tree freeze for ultraprune

Wladimir laanwj at gmail.com
Thu Oct 11 11:12:15 UTC 2012

On Thu, Oct 11, 2012 at 12:51 PM, Wladimir <laanwj at gmail.com> wrote:
> On Wed, Oct 10, 2012 at 8:40 PM, Jeff Garzik <jgarzik at 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.


More information about the bitcoin-dev mailing list