| Re: [paho-dev] want help with bug triage for the python library? |
We don't have a global Paho policy but maybe it's worth drawing one up?
The approach I take, which I developed through my own experience, is this:
- if it's a bone fide bug, and I can reproduce it or see from
inspection, then I label it as a bug, and assign it to a milestone. My
milestones include a backlog milestone for those I'll get to when I have
nothing else to do, or when I feel motivated.
- if it's an enhancement, I label it as such, and also ideally assign it
to a milestone.
- if it's a question, I label it as such. It might transform into a bug
or enhancement with further analysis - I might label it as "more info
needed". If I ask for more information, and none is forthcoming in a
month or two, then I close it, with a message something like "feel free
to reopen if you have more information". If I think the question is
answered, I'll close it with a message saying so, again after a delay of
a week, or month or two, whatever feels appropriate. The raiser can
reopen it or create another issue if they like, which is sometimes (but
not frequently) provoked by my closing it.
- if it looks like a possible bug, but I need more information to be
able to reproduce or confirm, I'll label it "more info needed", and
state in the issue what info I'm looking for. If we get to the problem,
then I'll categorize it as bug/enhancement/question as above. If there
is no more info or interaction after a period of time (see above) then I
will close it, saying that the reason is because of the lack of
information, and expecting the issue to be reopened if the raiser wants
to and supplies more information.
I haven't done this totally consistently, but the it does help me focus
on what's important to me and users.
It does take time to do this triage, but I think it's worth it.
Ian Craggs
On 17/10/2023 14:05, Greg Troxel via paho-dev wrote:
> Peter Silva via paho-dev <paho-dev@xxxxxxxxxxx> writes:
>
>> I'm wondering if the python maintainers want some help with bug
>> triage... it seems like there are many "support" issues sitting available.
>> I might be able to help with support type requests... here is some sample
>> followup on my part.
>>
>> https://github.com/eclipse/paho.mqtt.python/issues/744
>> https://github.com/eclipse/paho.mqtt.python/issues/745
>>
>> A lot of them are clearly just mistakes (complaints that
>> don't refer to the correct library... like this:
>>
>> https://github.com/eclipse/paho.mqtt.python/issues/740
>>
>> With a little more information about criteria for triage, I might be able
>> to at least ask for more information, and perhaps close some bugs.
> In the absence of getting permission to close, it might be useful to
> respond and ask the submitters to close the bugs themselves, when they
> are questions or incorrect. I generally find that it helps a project to
> clean up an issue tracker, and the only way is to start.
> _______________________________________________
> paho-dev mailing list
> paho-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/paho-dev
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/paho-dev