[Bf-committers] About triaging bugs in the tracker
sergey.vfx at gmail.com
Wed Sep 13 15:54:15 CEST 2017
Just wanted to make a quick not to state few points:
- It's always a good idea to triage reports right away. Without letting
them to grow mold of them.
- When you see a legitimate bug report, which has all information (and
especially if you can reproduce it) please assign the bug right away to
module owner or maintainers.
Point here is: if you're adding comment like "<Name>, please have a look"
the report will get lost in a pile of work real quickly, and nobody will
ever be able to figure out which reports he/she needs to look into.
However, if the report is assigned right away, everyone can easily see all
the reports which needs attention.
- Be more strict on what is a bug. If something is behaving according to
the current design / algorithm, it's not a bug. We simply can not afford
making every area of Blender ideal. Need to compromise somewhere. Make a
note in the TODO list and close the report (or move it from Bug to TODO if
- Do not consider list of reports assigned to you as something what one
expects you to fix. It's more like "have a look here, you have knowledge to
move fix forward". If it's not really your area, re-assign to someone who's
area it belongs to.
- Do not forget to check reports assigned to you every so often. Having
reports which are open for months without reply is not really good.
Have a quick look, it's rather fast to identify if it's a bug in code or
limitation of design / algorithm. If it's a bug, drop a line "Hey, looks
like a bug to me, will have a look", if it's not close as TODO.
With best regards, Sergey Sharybin
More information about the Bf-committers