[Tracker-discuss] bugs.python.org schema redesign

"Martin v. Löwis" martin at v.loewis.de
Tue Mar 24 21:48:41 CET 2009


R. David Murray wrote:
> On Tue, 24 Mar 2009 at 20:45, "Martin v. L�wis" wrote:
>>> "Feedback pending" reminds me of the "customer pending" status in our
>>> trouble ticket issue tracker.  But 'feedback pending' is too ambiguous.
>>> Whose feedback is pending?  I think you want it to be the submitter, in
>>> which case it should say that, I think.
>>
>> Any kind of followup should close the issue.
> 
> Except for followup that says don't close this issue, I presume?

Oops: Any kind of followup should *reopen* the issue (i.e. not close it)

Pending should be used with "I believe you are mistaken, and here is
why. No need to reply", or with "It's been a long time. If you are still
around, please confirm that the issue still exists".

Once we have autoclose, after 14 days, there will be a second message,
"this is now autoclosed", reminding the submitter that he didn't
respond. If then nobody still responds, there is agreement that the
issue deserves to be closed.

>> Why do you think so? The question really is "who should look at this",
>> and, in case of these two components, the answer is "a Mac expert"
>> or "a Windows expert" (just like for any other component).
> 
> Because a problem could be a problem with, say, a particular
> library module, but only shows up on the Mac (or the submitter has
> only seen it on a Mac).

The mac expert (or anybody performing triage) should then reclassify.

The same can happen to any other issue. It crashes in in httplib,
but the actual bug is somewhere down in the reference counting of
Unicode strings. Things get misclassified - no problem.

> Well, the motivation for it would be so that someone who was maintainer
> of a specific module or set of modules could easily find bugs against
> just those, instead of having to fish through all bugs marked "Library".
> But I suppose we could have triage assign them, instead, if we continue
> to have enough active triage people.

Maintainers wishing new component categories for their issues will
get them right away. Likewise, if you tell me that you found 20 issues
for xyz, I can create a component in no time.

> Speaking of which, is there somewhere where the list Daniel gathered
> of people who wanted certain classes of bugs assigned to them is
> posted?  I should probably have that in hand while doing triage.

Not sure - Daniel should certainly have it.

Regards,
Martin


More information about the Tracker-discuss mailing list