June 04, 2019
On Tue, 2019-06-04 at 00:16 +0000, Nicholas Wilson via Digitalmars-d wrote:
> On Monday, 3 June 2019 at 20:43:18 UTC, Walter Bright wrote:
> > On 6/3/2019 1:19 PM, H. S. Teoh wrote:
> > > It's common practice.  Doesn't make it right, though.
> > 
> > We're not doing it. Although proposals come by now and then to do such purges, I've been able to stop them before they've been implemented.
> 
> *cough* D1 bug reports *cough*

Are they issues/merge requests still applicable to the D mainmline
codebase? If yes, then edit it to remove the D1 label; if no, close the
issue/merge request as being no longer relevant to the codebase.

-- 
Russel.
===========================================
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk



June 04, 2019
On Monday, 3 June 2019 at 20:43:18 UTC, Walter Bright wrote:
> On 6/3/2019 1:19 PM, H. S. Teoh wrote:
>> It's common practice.  Doesn't make it right, though.
>
> We're not doing it. Although proposals come by now and then to do such purges, I've been able to stop them before they've been implemented.

The bigger problem is how it is completely unmanaged. There's no one that reviews the reported issues and sets a severity level. That's all set by whoever makes the report. I've come across a few issues that are solved, either that they always worked and were never really issues. Or they were inadvertently fixed by something else. There's also a lot of easy issues that aren't flagged as easy to fix cause no one is reviewing them, and the person that reports them may not know. This all creates noise for issues being resolved. People looking for issues will find them, it not a good enough excuse. It basically translates to, this list is only for people that have the time to waste looking through an unmanaged mess.


June 04, 2019
On Monday, 3 June 2019 at 19:52:34 UTC, Russel Winder wrote:
> On Mon, 2019-06-03 at 12:07 -0700, Walter Bright via Digitalmars-d wrote:
>> 
> […]
>> There's no purpose to closing things on github just because they've
>> aged below
>> the fold.
>
> Lots of projects delete all open issues that are over x months old (for
> some x usually > 12 and < 36) entirely for marketing purposes of not
> having old issues that are not actioned. Seems like un-professional
> behaviour to me.

The proper course of action would be to go through old bugs and verify them whether they can be closed (D1 bugs, bugs in phobos modules that don't exist anymore, bugs in deprecated featuers) or whether they still are reproducible (can't reproduce - can't fix) in latest version.
August 10, 2019
On 6/4/2019 12:32 AM, Russel Winder wrote:
> On Tue, 2019-06-04 at 00:16 +0000, Nicholas Wilson via Digitalmars-d
>> *cough* D1 bug reports *cough*
> Are they issues/merge requests still applicable to the D mainmline
> codebase? If yes, then edit it to remove the D1 label; if no, close the
> issue/merge request as being no longer relevant to the codebase.

The D1 only ones were all tagged as D1.

You can find 94 such open issues:

https://issues.dlang.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&component=dmd&list_id=227300&product=D&query_format=advanced&version=D1%20%28retired%29
August 10, 2019
On 6/4/2019 7:26 AM, Exil wrote:
> The bigger problem is how it is completely unmanaged. There's no one that reviews the reported issues and sets a severity level. That's all set by whoever makes the report. I've come across a few issues that are solved, either that they always worked and were never really issues. Or they were inadvertently fixed by something else.

Did you update their bugzilla status?
August 10, 2019
On 6/3/2019 2:44 PM, H. S. Teoh wrote:
> On Mon, Jun 03, 2019 at 01:17:02PM -0700, Walter Bright via Digitalmars-d wrote:
>> I guess no good deed goes unpunished. I haven't changed my mind,
>> however, about hiding the bug list for marketing porpoises.
> Marketing is run by porpoises?  That... explains a lot. :-D

Just chicken to see if anyone reads my posts :-)
August 10, 2019
On 6/4/2019 2:08 PM, JN wrote:
> The proper course of action would be to go through old bugs and verify them whether they can be closed (D1 bugs, bugs in phobos modules that don't exist anymore, bugs in deprecated featuers) or whether they still are reproducible (can't reproduce - can't fix) in latest version.

If you want to dig in and help with this, your help is welcome!
August 10, 2019
On Tuesday, 4 June 2019 at 21:08:35 UTC, JN wrote:
> On Monday, 3 June 2019 at 19:52:34 UTC, Russel Winder wrote:
>> On Mon, 2019-06-03 at 12:07 -0700, Walter Bright via Digitalmars-d wrote:
>>> 
>> […]
>>> There's no purpose to closing things on github just because they've
>>> aged below
>>> the fold.
>>
>> Lots of projects delete all open issues that are over x months old (for
>> some x usually > 12 and < 36) entirely for marketing purposes of not
>> having old issues that are not actioned. Seems like un-professional
>> behaviour to me.
>
> The proper course of action would be to go through old bugs and verify them whether they can be closed (D1 bugs, bugs in phobos modules that don't exist anymore, bugs in deprecated featuers) or whether they still are reproducible (can't reproduce - can't fix) in latest version.

For the past 1 month I started looking at the oldest bugs for dmd, closing the D1 only bugs and trying to fix those that I know how to fix. You will see that there are only 6 bugs with an id < 1000 (in dmd) now, while there were more than 30 when I started. It's a slow process because many of the old bugs are really hard to fix, but I hope that at some point I will have closed all issues < 3000.
August 10, 2019
On Saturday, 10 August 2019 at 11:10:14 UTC, RazvanN wrote:
> 
>
> For the past 1 month I started looking at the oldest bugs for dmd, closing the D1 only bugs and trying to fix those that I know how to fix. You will see that there are only 6 bugs with an id < 1000 (in dmd) now, while there were more than 30 when I started. It's a slow process because many of the old bugs are really hard to fix, but I hope that at some point I will have closed all issues < 3000.

Wow. Good luck.
August 10, 2019
On Saturday, 10 August 2019 at 07:57:04 UTC, Walter Bright wrote:
> On 6/4/2019 7:26 AM, Exil wrote:
>> The bigger problem is how it is completely unmanaged. There's no one that reviews the reported issues and sets a severity level. That's all set by whoever makes the report. I've come across a few issues that are solved, either that they always worked and were never really issues. Or they were inadvertently fixed by something else.
>
> Did you update their bugzilla status?

Nope, I've closed reports in the past that were duplicates, had no replies or any interest. Until I closed it, then there people fighting over it, one person saying they were going to work on it. They never did work on it. Its the wild west, I'm not going to make changes to it when anyone can undo those changes.