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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RX9F2-0003ok-0H for bitcoin-development@lists.sourceforge.net; Sun, 04 Dec 2011 10:24:16 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.161.175 as permitted sender) client-ip=209.85.161.175; envelope-from=witchspace81@gmail.com; helo=mail-gx0-f175.google.com; Received: from mail-gx0-f175.google.com ([209.85.161.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-MD5:128) (Exim 4.76) id 1RX9Ez-0005Hn-Ox for bitcoin-development@lists.sourceforge.net; Sun, 04 Dec 2011 10:24:15 +0000 Received: by ggnh1 with SMTP id h1so5466730ggn.34 for ; Sun, 04 Dec 2011 02:24:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.152.65 with SMTP id uw1mr952681obb.10.1322994248327; Sun, 04 Dec 2011 02:24:08 -0800 (PST) Received: by 10.182.63.167 with HTTP; Sun, 4 Dec 2011 02:24:08 -0800 (PST) Date: Sun, 4 Dec 2011 11:24:08 +0100 Message-ID: From: John Smith To: Bitcoin Dev Content-Type: multipart/alternative; boundary=f46d0444ef0336230304b3419a8f X-Spam-Score: -0.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 (witchspace81[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.1 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in digit (witchspace81[at]gmail.com) 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1RX9Ez-0005Hn-Ox Subject: [Bitcoin-development] Closing issues on github 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: Sun, 04 Dec 2011 10:24:16 -0000 --f46d0444ef0336230304b3419a8f Content-Type: text/plain; charset=ISO-8859-1 Hi, This weekend I closed some old github issues that are no longer reproducible in more recent versions, or needed input from the submitter but were stalling for months. I've also closed some issues that deal purely with Wx UI issues like this one: https://github.com/bitcoin/bitcoin/issues/425 I think my statement is valid, that we no longer support the old UI? Or maybe some people want to take up maintenance of the old UI? I don't think that has very high priority, and should probably not be in the main project. Some of the older issues are absolutely still relevant, but 150+ open issues is not something to be proud of, and I wonder how other open source projects deal with this without too much stepping on people's toes :-) JS --f46d0444ef0336230304b3419a8f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

This weekend I closed some old github issues that are no longer = reproducible in more recent versions, or needed input from the submitter bu= t were stalling for months.

I've also closed some issues that d= eal purely with Wx UI issues like this one:

https://githu= b.com/bitcoin/bitcoin/issues/425

I think my statement is valid, = that we no longer support the old UI? Or maybe some people want to take up = maintenance of the old UI? I don't think that has very high priority, a= nd should probably not be in the main project.

Some of the older issues are absolutely still relevant, but 150+ open i= ssues is not something to be proud of, and I wonder how other open source p= rojects deal with this without too much stepping on people's toes :-) <= br>
JS
--f46d0444ef0336230304b3419a8f--