On Friday, February 24, 2012 19:51:21 H. S. Teoh wrote:
> What's the convention on resolving issues on the bug tracker?
> 
> I just investigated issue 6709, and it appears that it's not a Phobos bug, but a bug in /bin/ip. Should I go ahead and resolve it?

Well, if it's not a bug in Phobos, and you can't reasonably create a fix which works around the problem, then I don't see what else you can do.

- Jonathan M Davis

On Fri, Feb 24, 2012 at 07:52:18PM -0800, Jonathan M Davis wrote:
> On Friday, February 24, 2012 19:51:21 H. S. Teoh wrote:
> > What's the convention on resolving issues on the bug tracker?
> > 
> > I just investigated issue 6709, and it appears that it's not a Phobos bug, but a bug in /bin/ip. Should I go ahead and resolve it?
> 
> Well, if it's not a bug in Phobos, and you can't reasonably create a fix which works around the problem, then I don't see what else you can do.

What I was wondering is whether just anyone can resolve the bug vs. someone designated.


T

-- 
It is the quality rather than the quantity that matters. -- Lucius Annaeus Seneca

On Friday, February 24, 2012 20:15:01 H. S. Teoh wrote:
> On Fri, Feb 24, 2012 at 07:52:18PM -0800, Jonathan M Davis wrote:
> > On Friday, February 24, 2012 19:51:21 H. S. Teoh wrote:
> > > What's the convention on resolving issues on the bug tracker?
> > > 
> > > I just investigated issue 6709, and it appears that it's not a Phobos bug, but a bug in /bin/ip. Should I go ahead and resolve it?
> > 
> > Well, if it's not a bug in Phobos, and you can't reasonably create a fix which works around the problem, then I don't see what else you can do.
> 
> What I was wondering is whether just anyone can resolve the bug vs. someone designated.

Well... Technically speaking, anyone can. No special permissions are required. And I'm not aware of any official policies on the matter. But if you close a bug, you should be certain that it _should_ be closed, and make sure that you comment with the reasoning for it.

- Jonathan M Davis