On Sat, Dec 26, 2015 at 5:15 PM, Justus Ranvier via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:

On 12/26/2015 05:01 PM, Pieter Wuille via bitcoin-dev wrote:
> I think the shortest reasonable timeframe for an uncontroversial
> hardfork is somewhere in the range between 6 and 12 months.

This argument would hold more weight if it didn't looks like a stalling
tactic in context.

I think you'll find that there hasn't been stalling regarding an uncontroversial hard-fork deployment. You might be confusing an uncontroversial hard-fork decision instead with how developers have brought up many issues about various (hard-forking) block size proposals.... I suspect this is what you're intending to mention instead, given your mention of "capacity emergencies" and also the subject line.

6 months ago, there was a concerted effort to being the process then,
for exactly this reason.

The uncontroversial hard-fork proposals from 6 months ago were mostly along the lines of jtimon's proposals, which were not about capacity. (Although, I should say "almost entirely uncontroversial"-- obviously has been some minor (and in my opinion, entirely solvable) disagreement regarding prioritization of deploying a jtimon's uncontroversial hard-fork idea I guess, seeing as how it has not yet happened.)

After 6 months of denial, stonewalling, and generally unproductive
fighting, the need for proactivity is being acknowledged with no
reference to the delay.

There wasn't 6 months of "stonewalling" or "denial" about an uncontroversial hard-fork proposal. There has been extensive discussion regarding the controversial (flawed?) properties of other (block size) proposals. But that's something else. Much of this has been rehashed ad nauseum on this mailing list already... thankfully I think your future emails could be improved and made more useful if you were to read the mailing list archives, try to employ more careful reasoning, etc. Thanks.

If the network ever ends up making a hasty forced upgrade to solve a
capacity emergency the responsibility for that difficulty will not fall
on those who did their best to prevent emergency upgrades by planning ahead.

("Capacity emergency" is too ambiguous in this context because of the competing concerns and tradeoffs regarding transaction rate capacity exhaustion vs. p2p low-bandwidth node bandwidth exhaustion.)

- Bryan
http://heybryan.org/
1 512 203 0507