Bug Priorities and Status #71418
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#71418
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Bug Priorities and Status
This proposal intents to align bug priorities and status with Blender triaging process .
Bug priorities should be distinct from status. Status should give us a snapshot of where in the bug fix flow this report is. Priorities should reflect the impact an issue has in the work of the users, not our development planning.
The proposed status are:
The proposed priorities are:
Added subscribers: @dfelinto, @Sergey
Added subscriber: @1D_Inc
Sounds nice)
But here is a bug definition problem:
Reported issue that matches the roadmap leads to a simple definition of an issue as a bug - as software issue.
Reported issue that contradicts the roadmap can be both a roadmap design mistake or a misunderstanding of the roadmap by the user. So such issue can be defined as workflow issue, that may need some additional semantic clarifiactions, including cases of uses, task examples, workflow comparisons, etc. It is always hard to define.
Such system can require well-defined multy-industry semantic core to handle and observe workflow issues (priorities, problem coverage, areas of uses, etc.) to protect the roadmap or heal it from gross design mistakes.
Added subscriber: @nokipaike
Sometimes bug reports that are not bugs but contain useful information, could be directed to devtalk to start a discussion (providing precise information that helps the user how to do it) instead of making them lose in nothing, especially by those new users who do not they know the rules of the community.
Professionals who come from outside, and have difficulties, one of the first things they do is report a bug-issue-feedback here ...
Added subscriber: @lichtwerk
We try to direct them to devtalk, see https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook, do you think the playbook can be improved upon?
@lichtwerk well, without thinking too much I would inform people of the existence of devtalk with a brief explanation of its purpose and invite them to do research on it to deepen or expand topics ....
Added subscriber: @merlinstail
It would be more consise to define priorities as:
None,
Low,
Medium,
High,
Critical
These are pretty standard definitions for priority, and while I appreciate that blender does things a little differently, I see no need for floral priority names.
Sounds reasonable)
Especially if to take in account workflow issues, that cannot be determined quickly, and sometimes years of production tests are needed to locate and define a problem.
Yes, they do.
Added subscriber: @MaciejJutrzenka
i think that developers should focus on just fixing.. not haveing to spend on working out is the bug true.. or asking user what GPU he have or crap like that...
triaging is not really a common word, i would use more simple names my propose are.
on top of this we could have as we have now priorities..
however i would just rate it from. 0 to 5 for example or just very low low normal medium etc..
Added subscriber: @rjg
The list of proposed status looks good. I consider the priorities suggested by @merlinstail better as well.
Added subscriber: @EAW
Current problem and solution:
For example let's say Developer works on new bevel tool.. He would like to see what problems people had in past or bugs with bevel.. U can't... U can't even filter Bug based on System user is useing. not even mentioning GPU or driver. Whole bug report is just random text. with tittle.
we keep code versioning. of blender. and we ask people to give what blender they use but we don't use this information at all.. u can't even filter.. is the bug from 2.79 or 2.8 And what worse. system dosn't automaticlly provide part of code that might make bug. For example if user report Bug about bevel in 2.81.. system will show all latest changes in code about bevel.. before 2.81.. also if developer is working on bevel.. system would show all reports with bevel tag. simpe as that.
currently big % of bug reports are even fixed.. but we didn't even know this.. because a) developer dosn't know about report. b) forgot to close the bug report.
so for example if guy.. is reporting bug in 2.79 about compositor... system checks if there was any change in code in compositor section. after 2.79 if there is 0 system allow bug to be reported.. if there was some code.. system tells user.. to check with for example version 2.81... is bug still happening.. and simply dosn't allow to make report.
on top of this we could add system that ranks bug reports. for example if bug report is done by user who made 10 reports and all where confirmed by developers.. than his next bug report instantly have high priority.
Changed status from 'Confirmed' to: 'Resolved'
Fully implemented since late December 2019.