Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <etotheipi@gmail.com>) id 1UH2x1-0005u5-DV
	for bitcoin-development@lists.sourceforge.net;
	Sun, 17 Mar 2013 02:03:55 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.173 as permitted sender)
	client-ip=209.85.220.173; envelope-from=etotheipi@gmail.com;
	helo=mail-vc0-f173.google.com; 
Received: from mail-vc0-f173.google.com ([209.85.220.173])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UH2wx-0007BC-I1
	for bitcoin-development@lists.sourceforge.net;
	Sun, 17 Mar 2013 02:03:55 +0000
Received: by mail-vc0-f173.google.com with SMTP id gd11so2174071vcb.18
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 16 Mar 2013 19:03:46 -0700 (PDT)
X-Received: by 10.220.108.69 with SMTP id e5mr13410253vcp.47.1363485826066;
	Sat, 16 Mar 2013 19:03:46 -0700 (PDT)
Received: from [192.168.1.85] (c-76-111-96-126.hsd1.md.comcast.net.
	[76.111.96.126])
	by mx.google.com with ESMTPS id j5sm14234854vdv.13.2013.03.16.19.03.44
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Sat, 16 Mar 2013 19:03:45 -0700 (PDT)
Message-ID: <51452473.1040301@gmail.com>
Date: Sat, 16 Mar 2013 22:03:31 -0400
From: Alan Reiner <etotheipi@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:17.0) Gecko/20130221 Thunderbird/17.0.3
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CABsx9T050Zia=5Xy4fRh_RtjOQzAVi-UPKmhYCuKbdZTF3U7dA@mail.gmail.com>
In-Reply-To: <CABsx9T050Zia=5Xy4fRh_RtjOQzAVi-UPKmhYCuKbdZTF3U7dA@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(etotheipi[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UH2wx-0007BC-I1
Subject: Re: [Bitcoin-development] 0.8.1 plan
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 17 Mar 2013 02:03:55 -0000

On 03/16/2013 09:13 PM, Gavin Andresen wrote:
> I chose May 15 arbitrarily; two months seems like a reasonable 'quick'
> amount of time to give people to upgrade/workaround.
>

Maybe you should wait until after the Bitcoin Conference -- if something
goes wacky on May 15th but then everyone is getting on a plane to go to
San Jose two days later, it may create unnecessary stress.  It's
probably not a big deal, but if the date is arbitrary anyway, why not
just push back one more week?

-Alan