[Bf-committers] Tracker curfew to start on Monday

Dalai Felinto dfelinto at gmail.com
Fri Dec 20 17:15:08 CET 2019


On Monday, Blender begins a tracker curfew.
Please check the teaser video: https://www.youtube.com/watch?v=HDE2ARiN1a0

A more complete document will follow suit, but the gist is: from now on the
Blender Foundation is going to adhere to a strict definition of what a bug

* It is only a bug if the code was intended to work and it fails, or when a
an issue used to work and it fails.
* It is only a bug if the module is in active maintenance. Otherwise it
might be registered as known issue.
* If a bug fix takes more than a day, it is not a bug, it is a development
task (if parts of the module plans) or a feature request (which we don’t
support at the moment).
* If a bug won’t be worked on for the upcoming 6 months, it is not a bug,
it is a known issue that needs to be documented.

The developers under contract will dedicate 2 full-days a week to work in
the tracker to re-triage issues, fix bugs and patch review.

Some stats following this definition. From a universe of 2,042 open reports
Blender has:
  * 631 untriaged reports.
  * 37 confirmed high priority bugs.
  * 1,367 reports that may be either a bug or a known issue

In the end the tracker curfew is to bring confirmed bugs down to a
manageable number (~200). There is a similar goal for patch review, but I
will leave this for the official code.blender.org post next week.

Have a great weekend,

More information about the Bf-committers mailing list