From: John Smith <witchspace81@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Closing issues on github
Date: Sun, 4 Dec 2011 11:24:08 +0100 [thread overview]
Message-ID: <CAJNQ0ssW4od3tA5vdASEs4KxZ7-UsxEjWT7NSc0dcWEzrkcH9w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 745 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1397 bytes --]
next reply other threads:[~2011-12-04 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 10:24 John Smith [this message]
2011-12-04 14:22 ` Luke-Jr
2011-12-04 15:31 ` Wladimir
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJNQ0ssW4od3tA5vdASEs4KxZ7-UsxEjWT7NSc0dcWEzrkcH9w@mail.gmail.com \
--to=witchspace81@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox