[Bf-committers] Automated Bug Report Classification

Sergey Sharybin sergey.vfx at gmail.com
Wed Nov 2 09:41:42 CET 2016


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

More information about the Bf-committers mailing list