Re: [Scons-dev] bug prune

2019-09-05 Thread Andrew Featherstone
Expanding on Russel's comment, the SCons project is a broad church that nominally supports a very large number of languages. I think old issues reflect the relative interest from the comminity for supporting a particular language and/or feature of SCons (e.g. people care a lot more about continued

Re: [Scons-dev] bug prune

2019-09-05 Thread Bill Deegan
O.k. I'll try to get this setup this weekend. On Thu, Sep 5, 2019 at 3:47 AM Russel Winder wrote: > On Tue, 2019-09-03 at 11:44 -0700, Bill Deegan wrote: > > On one hand dropping the number of open bugs will have significant > > appearance/PR improvements. > > (I've seen comments saying 600+

Re: [Scons-dev] bug prune

2019-09-05 Thread Russel Winder
On Tue, 2019-09-03 at 11:44 -0700, Bill Deegan wrote: > On one hand dropping the number of open bugs will have significant > appearance/PR improvements. > (I've seen comments saying 600+ bugs outstanding the project must not be > still alive). I'd say having a lot of open bugs in a project that

Re: [Scons-dev] bug prune

2019-09-03 Thread Bill Deegan
On one hand dropping the number of open bugs will have significant appearance/PR improvements. (I've seen comments saying 600+ bugs outstanding the project must not be still alive). But dropping 620 of 680 bugs because they're stale, but possibly still unresolved issues probably isn't the best.

Re: [Scons-dev] bug prune

2019-09-03 Thread Jonathon Reinhart
That makes sense, Mats. Thanks for the additional insight. On Mon, Sep 2, 2019, 10:30 Mats Wichmann wrote: > On 9/2/19 8:03 AM, Jonathon Reinhart wrote: > > Note that you can subscribe to a GitHub issue without commenting. This > > is preferred as it avoids spamming all currently-subscribed

Re: [Scons-dev] bug prune

2019-09-02 Thread Mats Wichmann
On 9/2/19 8:03 AM, Jonathon Reinhart wrote: > Note that you can subscribe to a GitHub issue without commenting. This > is preferred as it avoids spamming all currently-subscribed users. > > Also, I think mass/automated bug closing needs to be done very > conservatively. Closing an issue doesn't

Re: [Scons-dev] bug prune

2019-09-02 Thread Jonathon Reinhart
Note that you can subscribe to a GitHub issue without commenting. This is preferred as it avoids spamming all currently-subscribed users. Also, I think mass/automated bug closing needs to be done very conservatively. Closing an issue doesn't make the bug go away. There are projects that have bots

Re: [Scons-dev] bug prune

2019-08-31 Thread Bill Deegan
Dirk, If you can create a HTML dump, I can put it up on the scons.org webserver and link to it. And then maybe we create a repo to check in all the source files with scripts to regen? -Bill On Sat, Aug 31, 2019 at 5:09 AM Dirk Bächle wrote: > Hi, > > this approach sounds good to me too. I

Re: [Scons-dev] bug prune

2019-08-31 Thread Dirk Bächle
Hi, this approach sounds good to me too. I just wanted to mention that I have all the old Tigris Issues (and user and developer mails) archived on my local machine. They're stored in a simple text-ish format that can be read into corresponding Python classes. My plan is still to write a small

Re: [Scons-dev] bug prune

2019-08-27 Thread Gary Oberbrunner
I think this would be great. I'll help review the bugs-to-be-closed. -- Gary On Tue, Aug 27, 2019 at 8:50 AM Mats Wichmann wrote: > > Just to pull some thoughts together: > > there are currently 679 open scons issues on github. > > That number drops to 92 if you select only ones which have had

[Scons-dev] bug prune

2019-08-27 Thread Mats Wichmann
Just to pull some thoughts together: there are currently 679 open scons issues on github. That number drops to 92 if you select only ones which have had a modification since the big migration from tigris. Try this query: is:issue is:open updated:>=2018-02-10 or as a link: