On Thu, Oct 11, 2012 at 12:51 PM, Wladimir <laa...@gmail.com> wrote: > On Wed, Oct 10, 2012 at 8:40 PM, Jeff Garzik <jgar...@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 ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
