From: Jeff Garzik <jgarzik@exmulti•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Post-0.7.1 tree freeze for ultraprune
Date: Wed, 10 Oct 2012 14:40:55 -0400 [thread overview]
Message-ID: <CA+8xBpdLo+VoHiJNJWNn+NPHj9v33=bSXBhkBeoLr73z-qFrBQ@mail.gmail.com> (raw)
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.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti•com
next reply other threads:[~2012-10-10 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 18:40 Jeff Garzik [this message]
2012-10-11 10:51 ` Wladimir
2012-10-11 11:12 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+8xBpdLo+VoHiJNJWNn+NPHj9v33=bSXBhkBeoLr73z-qFrBQ@mail.gmail.com' \
--to=jgarzik@exmulti$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox