On Monday, September 19, 2011 11:00 AM, "Luke-Jr" <l...@dashjr.org> 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. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
