August 10, 2019 Re: Bug fix over a year old | ||||
---|---|---|---|---|
| ||||
Posted in reply to Exil | On 8/10/2019 6:10 AM, Exil wrote: > 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. Closing issues that have no replies or interest is not helpful. I asked if you updated the status for issues that are solved or always worked. > I'm not going to make changes to it when anyone can undo those changes. I'd reopen any issues that were closed just because they were old, too. |
August 10, 2019 Re: Bug fix over a year old | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter Bright | On Saturday, 10 August 2019 at 21:22:52 UTC, Walter Bright wrote:
> On 8/10/2019 6:10 AM, Exil wrote:
>> 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.
>
> Closing issues that have no replies or interest is not helpful. I asked if you updated the status for issues that are solved or always worked.
That's not true in the general case: there are many issues where you can't reach the reporter and he didn't leave a way to reproduce the issue. Then, there's simply no hope to fix the issue.
|
August 10, 2019 Re: Bug fix over a year old | ||||
---|---|---|---|---|
| ||||
Posted in reply to Seb | On 8/10/2019 2:31 PM, Seb wrote:
> That's not true in the general case: there are many issues where you can't reach the reporter and he didn't leave a way to reproduce the issue. Then, there's simply no hope to fix the issue.
That's different. I was talking about closing issues just because they were old.
|
August 10, 2019 Re: Bug fix over a year old | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter Bright | On Monday, 3 June 2019 at 20:17:02 UTC, Walter Bright wrote:
> Back in the 80s, I kept a bug list as a simple text file (yes, I'm that old, I wasn't even using email yet as a bug database).
I do this and I'm not even old.
Of course I still use things like Github Issues etc. but for some projects it's just easier to do it in ex. a text file because there are so few bugs.
|
August 11, 2019 Re: Bug fix over a year old | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter Bright | On Sat, Aug 10, 2019 at 12:58:42AM -0700, Walter Bright via Digitalmars-d wrote: > 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 :-) That ... eggsplains a few other things too(!). T -- Answer: Because it breaks the logical sequence of discussion. Question: Why is top posting bad? |
Copyright © 1999-2021 by the D Language Foundation