[Bf-committers] Automated Bug Report Classification

[Sergey Sharybin]

Hi,

Automatically closing reports is not a greatest idea at all. Sometimes we
have so much on our desks so can't keep track of all incomplete reports
even when the requested information was already provided. Closing such
reports would not be any helpful.

Raising to "Needs Triage" i'm also not fully convinced in. Quite often it's
more than two developers asking for some additional information. Setting
status to "Needs Triage" when second developer asks for more details will
be undesired. Then, sometimes we also have more than one user active in the
report, so it's not necesserily an author of report will give fully
qualified steps of reproducing the problem.

Should we move discussion from "how to do something automatically" (knowing
that automatic things fails a lot) to "how to attract more users to
communicate on dev.b.o" ? Human interacting with human is always better way
to go.

P.S. We have 150+ users at #blendercoders, so if one user replies to one
report per day in two days we have all reports nicely handled ;)


On Thu, Nov 3, 2016 at 6:08 AM, Aaron Carlisle <carlisle.aaron00 at gmail.com>
wrote:

> Something that would be nice here is also to automatically close reports
> that do not respond after being marked as in complete and also raising
> there priority back to needs triage. By the way,  the last thing here is my
> opinion and is something that can be discussed separately.
>
> - Aaron
>
> On Nov 2, 2016 4:41 AM, "Sergey Sharybin" <sergey.vfx at gmail.com> wrote:
>
> Hi,
>
> Personally i have serious doubts such automation will indeed help and will
> not just cause frustration from users who simply receive automatic reply.
>
> Some points:
>
> - Replying that the report lacks details is not time consuming at all: you
> glance over the report and reply one of the templated replies.
> - It's not always needed to know all the details in all the reports. If the
> reports says "Revision XXX broke feature YYY" you can almost always check
> what's wrong in that commit. Some of the reports are also created after
> communication in IRC where all the details were discussed anyway.
> - It is much much much more important to have reproducible steps with a
> simple file specified in the report. I do not know how can you check
> whether bug can be or can not be reproduced automatically.
>
> The only thing which will help here in my opinion, is getting community
> more active. Everyone can drop to the bug report, test it and reply to a
> reporter that something can not be reproduced and that reported should try
> to isolate the problem more. Simple things like that.
>
> On Wed, Nov 2, 2016 at 5:53 AM, Eibriel <eibriel at eibriel.com> wrote:
>
> > Hi! If you are a developer dealing with bug reports I've a propossal for
> > Automated Bug Report Classification: https://wiki.blender.org/
> > index.php/User:Eibriel/Automated_Bug_Classification
> >
> > I would love to know if you think this project will actually help or not
> > to Blender development.
> >
> > I was thinking how to contribute to Blender taking advantage of
> > automation, and have this idea :P
> >
> > Bests!
> > Eibriel
> >
> > --
> > Eibriel
> > http://Eibriel.com
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > https://lists.blender.org/mailman/listinfo/bf-committers
> >
>
>
>
> --
> With best regards, Sergey Sharybin
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> https://lists.blender.org/mailman/listinfo/bf-committers
>



-- 
With best regards, Sergey Sharybin