Post-0.7.1 tree freeze for ultraprune

3 messages, 10 to 11 Oct 2012. Started by Jeff Garzik.

Wladimir J. van der Laan (2), Jeff Garzik

Jeff Garzik 10 Oct 2012, 18:40 UTC permalink original

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).

Common sense exceptions still apply (critical bug fixes, etc.)

Ultraprune does not need to be "perfect" to be pulled... this pull would occur at the beginning of 0.8, leaving lots of room for hammering out final details in-tree. The main hurdle is really getting everyone to ACK the overall design and direction of the ultraprune branch, especially Gavin.

Collecting those high-level design ACKs is more important to bitcoin overall than even fine-grained code review; code mistakes can be fixed in-tree during 0.8 development, once we all agree this is the correct _design_. The real code mistakes and "sharp edges" will only be found now with wide field testing.

For the record: yes, Design-ACK from me.

Wladimir J. van der Laan 11 Oct 2012, 10:51 UTC in reply to Jeff Garzik permalink original

On Wed, Oct 10, 2012 at 8:40 PM, Jeff Garzik <jgarzik@exmulti•com> wrote:

Quoted text (3 lines)

> 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

Wladimir J. van der Laan 11 Oct 2012, 11:12 UTC in reply to Wladimir J. van der Laan permalink original

On Thu, Oct 11, 2012 at 12:51 PM, Wladimir <laanwj@gmail•com> wrote:

Quoted text (9 lines)

> 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