On Thursday, 13 February 2014 at 20:00:29 UTC, Walter Bright wrote:
> On 2/13/2014 10:34 AM, francesco cattoglio wrote:
>> Also, the current open issues list is HUGE, cutting it down by
>> discarding outdated stuff would be nice. Or at least, would
>> *look* nice. Honestly, the first time I took a look at D I was
>> like "wait, is this a programming language or a testbed for some
>> strange compiler?" :P
>
> Restrict your search for open bugs to "D2" and "D1 & D2" and you'll be fine.

I never thought to do that as I have just gone by the "Bug Tracker" graphic on the website up until now. Interesting idea. Here is a chart comparing how the number of open bugs changes when those two filters are applied to the "Bug Tracker" queries.
                         Before   After
Regression               9        9
Blocker                  17       17
Critical                 69       63
Major                    221      206
Normal, minor, trivial   1923     1420
Enhancement              1153     866
All Open                 3392     2586

That large of a difference surprised me. Seems like it would help with the impression of quality to someone first coming to the site by displaying the data filtered for D2 instead. It also seems more accurate since the D1 only stuff is not really being worked on and that page presents sort of a TODO list.

Joseph

On 2/13/2014 6:07 PM, Daniel Murphy wrote:
> No, this doesn't work, because many many bugs are not marked correctly.  A bug
> being marked D1 often just means it's old.

Anyone can help out when they see miscategorized bugs by fixing the categories.

On Wednesday, 12 February 2014 at 08:57:21 UTC, Walter Bright wrote:
> On 2/11/2014 11:29 AM, Steven Schveighoffer wrote:
>> Thoughts? I closed the aforementioned bug as WONTFIX. Anyone is free to correct
>> that if you feel it's in error :)
>
> D1 is still in use. Just ignore D1 only bugs if you don't use D1. But to close
> them does a disservice to the existing D1 users.

What would be the negative impact on D1 users ? And how many people will be affected ?

As the "official support for D1" has been discontinued in 2012, shouldn't one expect the official bug tracker to close anything D1-related too ?

Last but not least, there is the risk that bugs, once fixed for D2, turns into D1 bugs, which would harm our statistics and may bug some other tools (bountysource ?). Take a look at #10217 as an example.

On Friday, 14 February 2014 at 05:27:14 UTC, Mathias LANG wrote:
> On Wednesday, 12 February 2014 at 08:57:21 UTC, Walter Bright wrote:
>> On 2/11/2014 11:29 AM, Steven Schveighoffer wrote:
>>> Thoughts? I closed the aforementioned bug as WONTFIX. Anyone is free to correct
>>> that if you feel it's in error :)
>>
>> D1 is still in use. Just ignore D1 only bugs if you don't use D1. But to close
>> them does a disservice to the existing D1 users.
>
> What would be the negative impact on D1 users ? And how many people will be affected ?
>


> As the "official support for D1" has been discontinued in 2012, shouldn't one expect the official bug tracker to close anything D1-related too ?

Why? Does it affect D2 in any way if D1 bugs are in the bug tracker(besides some meaningless stats)?. Just because it is offically deprecated and not supported doesn't not imply there is no support at all.
>
> Last but not least, there is the risk that bugs, once fixed for D2, turns into D1 bugs, which would harm our statistics and may bug some other tools (bountysource ?). Take a look at #10217 as an example.

So? Then change the version to D1 only.

Focus should be on actually fixing bugs, not some feelgood numbers coming out of the bug tracker stats. Besides, I doubt there is any real negative impact on D as a result of the bug tracker numbers at this stage. Maybe worry about that when evidence suggests otherwise.

Cheers,
ed

On Friday, 14 February 2014 at 06:07:01 UTC, ed wrote:
> On Friday, 14 February 2014 at 05:27:14 UTC, Mathias LANG wrote:
>> As the "official support for D1" has been discontinued in 2012, shouldn't one expect the official bug tracker to close anything D1-related too ?
>
> Why? Does it affect D2 in any way if D1 bugs are in the bug tracker(besides some meaningless stats)?. Just because it is offically deprecated and not supported doesn't not imply there is no support at all.

It affects me when I'm trying to file a bug, and looking through
already existing bugs, if 1000 of them are from an historical
project.

>> Last but not least, there is the risk that bugs, once fixed for D2, turns into D1 bugs, which would harm our statistics and may bug some other tools (bountysource ?). Take a look at #10217 as an example.
>
> So? Then change the version to D1 only.
>
> Focus should be on actually fixing bugs, not some feelgood numbers coming out of the bug tracker stats. Besides, I doubt there is any real negative impact on D as a result of the bug tracker numbers at this stage. Maybe worry about that when evidence suggests otherwise.

It's not necessarily about the numbers. It's the fact that now,
the project is 100% D2, 0% D1, and the D1 bugs are getting in our
way. In particular, since D1 is not supposed to be supported, it
makes little sense to support bug tracking for it. It's noise and
nothing more.

I think it would make more sense instead to have a good wiki/ddoc
page that clearly documents know issues in D1 that won't get
fixed, how they are triggered, and how to work around them.

IMO, once properly documented and identified, then the bug can
simply be closed as "won't fix".

On Tuesday, 11 February 2014 at 19:29:14 UTC, Steven Schveighoffer wrote:
> I noticed Vladimir closed a D1 bug as WORKSFORME, with an explanation that it is fixed in the latest version of D2 phobos, not realizing it was a D1 bug. (https://d.puremagic.com/issues/show_bug.cgi?id=1004)
>
> However, it brought up a discussion of what to do with D1 bugs. Should they be closed? If so, what should be the reason for closing? My impression is if the bug still exists (and I'm not advocating we test for it), we should close it as WONTFIX, since D1 is deprecated.
>
> Thoughts? I closed the aforementioned bug as WONTFIX. Anyone is free to correct that if you feel it's in error :)
>
> -Steve

I agree with you in this case.

D1 is in heavy commercial use at Sociomantic, and we are still submitting patches to DMD, and we frequently search bugzilla for open D1 bugs. But AFAIK *nobody* is using D1 Phobos.
The only remaining role of D1 Phobos, AFAIK, is to allow the D1 test suite to run.

I think that we should close all D1 Phobos bugs as WONTFIX. Realistically they are never going to be fixed, and I don't think anybody cares.
(Or, if the bug also applied to D2, but is already fixed in D2, I think it would be perfectly valid to mark it as FIXED).

"Walter Bright"  wrote in message news:ldjvs6$av1$1@digitalmars.com...

> > No, this doesn't work, because many many bugs are not marked correctly. A bug
> > being marked D1 often just means it's old.
>
> Anyone can help out when they see miscategorized bugs by fixing the categories.

And until that is complete, there is no reliable way to filter out D1 bugs. I've been marking them with "(D1 only)", so I know at least those ones are actually D1 bugs.

Is sociomantic _actually_ using D1 phobos and caring if those bugs get fixed?  If not we should close them. 

"ed"  wrote in message news:qpkejaxtasbzakgprzti@forum.dlang.org...

> > As the "official support for D1" has been discontinued in 2012, shouldn't one expect the official bug tracker to close anything D1-related too ?
>
> Why? Does it affect D2 in any way if D1 bugs are in the bug tracker(besides some meaningless stats)?. Just because it is offically deprecated and not supported doesn't not imply there is no support at all.

It affects the people using and maintaining the bug tracker due to the false positives it generates.

> > Last but not least, there is the risk that bugs, once fixed for D2, turns into D1 bugs, which would harm our statistics and may bug some other tools (bountysource ?). Take a look at #10217 as an example.
>
> So? Then change the version to D1 only.

No, this won't work, because you actually have two separate issues, one for D1 and one for D2, one fixed and the other open.  eg the changelog is generated from the list of RESOLVED FIXED bugs, and won't pick up ones that changed status.

> Focus should be on actually fixing bugs, not some feelgood numbers coming out of the bug tracker stats. Besides, I doubt there is any real negative impact on D as a result of the bug tracker numbers at this stage. Maybe worry about that when evidence suggests otherwise.

This is coming from the people who are fixing bugs.  This issues gets in the way of doing so.  I couldn't care less about the numbers. 

"Don"  wrote in message news:sqijjqlbiarapepraswf@forum.dlang.org... 

> I agree with you in this case.
> 
> D1 is in heavy commercial use at Sociomantic, and we are still submitting patches to DMD, and we frequently search bugzilla for open D1 bugs. But AFAIK *nobody* is using D1 Phobos.
> The only remaining role of D1 Phobos, AFAIK, is to allow the D1 test suite to run.
> 
> I think that we should close all D1 Phobos bugs as WONTFIX. Realistically they are never going to be fixed, and I don't think anybody cares.
> (Or, if the bug also applied to D2, but is already fixed in D2, I think it would be perfectly valid to mark it as FIXED).

Thankyou Don!  I thought that might be the case.

On 2/14/2014 2:22 AM, Daniel Murphy wrote:
> And until that is complete, there is no reliable way to filter out D1 bugs. I've
> been marking them with "(D1 only)", so I know at least those ones are actually
> D1 bugs.

Do a search for "D2" and "D1 & D2".


> Is sociomantic _actually_ using D1 phobos and caring if those bugs get fixed?

To reiterate, the D1 bugzilla issues stay as long as Sociomantic is using D1.