From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1R5s9V-0001EY-Gs for bitcoin-development@lists.sourceforge.net; Tue, 20 Sep 2011 04:41:49 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of mm.st designates 66.111.4.27 as permitted sender) client-ip=66.111.4.27; envelope-from=theymos@mm.st; helo=out3.smtp.messagingengine.com; Received: from out3.smtp.messagingengine.com ([66.111.4.27]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1R5s9U-0007OG-Fh for bitcoin-development@lists.sourceforge.net; Tue, 20 Sep 2011 04:41:49 +0000 Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id D43E42C079 for ; Tue, 20 Sep 2011 00:41:42 -0400 (EDT) Received: from web3.nyi.mail.srv.osa ([10.202.2.213]) by compute1.internal (MEProxy); Tue, 20 Sep 2011 00:41:42 -0400 Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id B569BB40207; Tue, 20 Sep 2011 00:41:42 -0400 (EDT) Message-Id: <1316493702.25740.140258143733145@webmail.messagingengine.com> X-Sasl-Enc: W5CuovjFHPimeLLeZ2ikqMpMsL8XbdVnxTDLHosLibRo 1316493702 From: "theymos" To: bitcoin-development@lists.sourceforge.net MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Mailer: MessagingEngine.com Webmail Interface References: <201109181930.59565.luke@dashjr.org> <201109191100.58100.luke@dashjr.org> In-Reply-To: <201109191100.58100.luke@dashjr.org> Date: Mon, 19 Sep 2011 23:41:42 -0500 X-Spam-Score: -1.5 (-) 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 (theymos[at]mm.st) -0.0 SPF_PASS SPF: sender matches SPF record 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 0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service X-Headers-End: 1R5s9U-0007OG-Fh Subject: Re: [Bitcoin-development] 0.4.x stable branch X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2011 04:41:49 -0000 On Monday, September 19, 2011 11:00 AM, "Luke-Jr" wrote: > The problem with the current development model is that bugfixes are > done alongside improvements, and code changes *always* have the > potential to introduce new bugs, no matter how careful anyone is. So > to stay on top of bugfixes right now implies risking new bugs being > introduced. What good is getting one bug fixed, if it comes with 20 > new yet-to-be-discovered bugs? A stable version is a good idea. This is why I'm still using 0.3.19 (with some modifications): none of the bugfixes after this version help me much, and I don't need any of the new features. I've also thought about starting an unofficial stable version with my modifications to 0.3.19 and some backported bugfixes.