Jump to page: 1 25  
Page
Thread overview
Close D1 bugs?
Feb 12, 2014
Daniel Murphy
Feb 12, 2014
Daniel Murphy
Feb 12, 2014
Peter Alexander
Feb 12, 2014
Walter Bright
Feb 13, 2014
Walter Bright
Feb 14, 2014
Daniel Murphy
Feb 14, 2014
Walter Bright
Feb 14, 2014
Daniel Murphy
Feb 14, 2014
Walter Bright
Feb 14, 2014
Daniel Murphy
Feb 15, 2014
Walter Bright
Feb 15, 2014
Walter Bright
Feb 15, 2014
Daniel Murphy
Feb 15, 2014
Walter Bright
Feb 15, 2014
Daniel Murphy
Feb 14, 2014
Joseph Cassman
Feb 14, 2014
w0rp
Feb 14, 2014
Brad Roberts
Feb 15, 2014
Walter Bright
Feb 15, 2014
Joseph Cassman
Feb 14, 2014
Mathias LANG
Feb 14, 2014
ed
Feb 14, 2014
monarch_dodra
Feb 14, 2014
Daniel Murphy
Feb 14, 2014
Don
Feb 14, 2014
Daniel Murphy
Feb 14, 2014
Walter Bright
Feb 14, 2014
Brad Roberts
Feb 14, 2014
Walter Bright
Feb 15, 2014
Don
Feb 15, 2014
Walter Bright
Feb 14, 2014
Dicebot
Feb 14, 2014
Dicebot
Feb 14, 2014
Jacob Carlborg
February 11, 2014
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
February 12, 2014
"Steven Schveighoffer"  wrote in message news:op.xa4tq0hzeav7ka@stevens-macbook-pro.local...

> 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 :)

The is the unfortunate consequence of putting a bug from two different projects in the same report.  Ideally the D1 portion would be WONTFIX, and the D2 part would be WORKSFORME/FIXED/etc.

Since we can't actually do that, I think we should just discard the D1 information and give it the appropriate status for D2.  After all, we're not going to fix the bug for 2.061 or 2.062 or 2.063 etc either, but we won't mark it WONTFIX because of that. 

February 12, 2014
On Tue, 11 Feb 2014 21:54:29 -0500, Daniel Murphy <yebbliesnospam@gmail.com> wrote:

> "Steven Schveighoffer"  wrote in message news:op.xa4tq0hzeav7ka@stevens-macbook-pro.local...
>
>> 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 :)
>
> The is the unfortunate consequence of putting a bug from two different projects in the same report.  Ideally the D1 portion would be WONTFIX, and the D2 part would be WORKSFORME/FIXED/etc.
>
> Since we can't actually do that, I think we should just discard the D1 information and give it the appropriate status for D2.  After all, we're not going to fix the bug for 2.061 or 2.062 or 2.063 etc either, but we won't mark it WONTFIX because of that.

Hm... there didn't seem to be any indication that it was D2 related. In any case, I was speaking about D1-only bugs.

-Steve
February 12, 2014
"Steven Schveighoffer"  wrote in message news:op.xa5ffvpceav7ka@stevens-macbook-pro.local...

> Hm... there didn't seem to be any indication that it was D2 related. In any case, I was speaking about D1-only bugs.

Ah. 

February 12, 2014
On Tuesday, 11 February 2014 at 19:29:14 UTC, Steven Schveighoffer wrote:
> However, it brought up a discussion of what to do with D1 bugs. Should they be closed?

Last time I asked about this, it was argued that D1 bugs should remain in case "someone" wants to fix them.

I'm against this because D1 is supposedly unsupported, and no one appears to be fixing D1 bugs anyway.

I think they should be closed as WONTFIX with a quick comment to say that D1 is unsupported.
February 12, 2014
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.
February 13, 2014
On Wed, 12 Feb 2014 03:57:25 -0500, Walter Bright <newshound2@digitalmars.com> 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.

I think leaving them open with hope it will be fixed when it likely will never happen is also a disservice.

Tell me, are you planning on accepting patches for D1 phobos ever?

-Steve
February 13, 2014
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.

Just deleting them would be a horrible disservice. Marking as
"WONTFIX" sounds reasonable to me. After all, since support got
dropped, "won't be fixed" sounds realistic.

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
February 13, 2014
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.
February 14, 2014
"Walter Bright"  wrote in message news:ldj88t$2hpa$1@digitalmars.com...

> Restrict your search for open bugs to "D2" and "D1 & D2" and you'll be fine.

No, this doesn't work, because many many bugs are not marked correctly.  A bug being marked D1 often just means it's old. 

« First   ‹ Prev
1 2 3 4 5