[Bf-committers] Triaging: any confirmed issue should be tagged to a module

[Dalai Felinto]

Hi,
This is a friendly reminder to follow the triaging process more closely [1].

At the moment there are around 80 tasks that are not tagged with any
of the module tags. That means these reports, known issues and bugs
won't ever be classified, found and fixed (respectively), since they
don't show in the modules queries and workboards.

To keep track of this there is a new global query called "Needs Module
Tag" to show all the reports that were not fully tagged [2].

Triaging team: please go over these tasks, tag them accordingly, and
remember the person who confirmed without a proper tag to do so next
time [3]. Focus on the bugs first, then the known issues.

Modules owners: if you want to include more tags in your module is
very simple. You need to tag the project task with it, and update the
queries accordingly [4].

Currently module-less tags from untagged reports [2]:
* Alembic
* Audio
* Compositing
* Dependency Graph
* Freestyle
* Images & Movies
* Modifiers
* Performance
* Translations

[1] - https://wiki.blender.org/wiki/Process/A_Bugs_Life
[2] - https://developer.blender.org → Maniphest →Needs Module Tag
[3] - e.g., "Confirmed reports should always be tagged to a module,
otherwise they don't show up in the queries and workboards."
[4] - Queries that need to be updated: "Needs Module Tag", the
module's "Bug", "Known Issue" and "Unclassified queries", the module
queries when changing a sub-module (e.g., if changing Text Editor, the
Python & Addons' queries need update too).

Thank you,
-Dalai-
--------------------------------------------------------------------
Dalai Felinto - dalai at blender.org - www.blender.org
Blender Development Coordinator