MIME-Version: 1.0
In-Reply-To: <CAOG=w-v0_dfZS2=XfKQzRZ9Vq2Z2YqUO2_cuvOheuUrD4dbYtw@mail.gmail.com>
References: <CADJgMzs0w4L7ma42RCzT5dYDcG2aY1_04G1khcFPFPE6mmB=-A@mail.gmail.com>
	<CAOG=w-v0_dfZS2=XfKQzRZ9Vq2Z2YqUO2_cuvOheuUrD4dbYtw@mail.gmail.com>
Date: Fri, 27 Nov 2015 11:14:10 +0100
Message-ID: <CABm2gDrjiNTNo3FZ82D3131g5gBEwfHCofdK9BeEPPZ6k-TzbQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Mark <mark@friedenbach.org>
Content-Type: multipart/alternative; boundary=001a113daab6d40e99052582f3cf
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Alternative name for CHECKSEQUENCEVERIFY (BIP112)
Precedence: list

--001a113daab6d40e99052582f3cf
Content-Type: text/plain; charset=UTF-8

On Nov 26, 2015 12:06 AM, "Mark Friedenbach via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Again my objection would go away if we renamed nSequence, but I actually
think the nSequence name is better...

I suggested to rename nSequence to nMaturity on this list even before the
bips and implementations were started, probably too late now.
Before the implementation "let's think about those naming details later".
After the implementation "now it's too late, now we would need to change
the implementation, this renaming is now unnecessarily disruptive".

Reminds me of refactors and major releases:
At the beginning of the release "not now, this will disrupt development of
feature X"
After feature X is merged or replaced by feature Y: "too late in the
release cycle, refactors should be done only at the beginning, at the end
is 'too risky' ".
Sigh, I hope I find the "right time" (not both too soon and too late like
this time), next time...

--001a113daab6d40e99052582f3cf
Content-Type: text/html; charset=UTF-8

<p dir="ltr"><br>
On Nov 26, 2015 12:06 AM, &quot;Mark Friedenbach via bitcoin-dev&quot; &lt;<a href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br>
&gt; Again my objection would go away if we renamed nSequence, but I actually think the nSequence name is better...</p>
<p dir="ltr">I suggested to rename nSequence to nMaturity on this list even before the bips and implementations were started, probably too late now.<br>
Before the implementation &quot;let&#39;s think about those naming details later&quot;.<br>
After the implementation &quot;now it&#39;s too late, now we would need to change the implementation, this renaming is now unnecessarily disruptive&quot;.</p>
<p dir="ltr">Reminds me of refactors and major releases:<br>
At the beginning of the release &quot;not now, this will disrupt development of feature X&quot;<br>
After feature X is merged or replaced by feature Y: &quot;too late in the release cycle, refactors should be done only at the beginning, at the end is &#39;too risky&#39; &quot;.<br>
Sigh, I hope I find the &quot;right time&quot; (not both too soon and too late like this time), next time...</p>

--001a113daab6d40e99052582f3cf--