Blender Winter of Quality - December and January project

Announcements
1

As announced in a previous post, the Blender developers will be focusing on quality for the next few weeks.
Also see an overview here.

Lead Engineer Sergey Sharybin gave a presentation last week about what is expected of the team, overall, and during this specific projects. You can view his talk here.

Some modules have presented plans for this Quality project:

  • Grease Pencil: plan including regressions or missing functionalities from 4.2, adding more tests, some cleanups
  • Nodes & Physics: short plan focused on fixing bug reports, some refactors.
  • Render & Cycles: mostly documentation! (and regular bug fixing)
  • Sculpt, Paint, Texture: the plan mostly consists of adding automasted testing, with some refactors
  • VFX and Video: @iss @aras_p and @eliphaz drew a plan for the VSE; as for the compositor it is mostly about finishing the work @OmarEmaraDev is doing as it will solve a few issues (still, a plan here)
  • Viewport and EEVEE: plan that aims to finish ongoing projects and improve testing. Of course, bug fixing will also continue.

Which hopefully guides and motivates contributions from the community! Any help is welcome, please don’t hesitate to reach out in the module channels.

As for the other modules:

With this effort, the goal is to get more fixes in, for a more stable Blender - with the end goal to have this type of task more integrated in the weekly workflow of the teams.

Edited 02-12-24 14:33 to add the plan for Sculpting, Animation, Pipeline, Compositor

16 Likes
2

A perfect opportunity to collect numbers and compare them end of December and end of January again. :smiley:

Open bugs per module (Low / Normal / High severity):

Module 2.12.2024 31.12 31.1
Animation & Rigging 20 / 273 / 0 20 / 277 / 4
Asset System 2 / 69 / 3 2 / 74 / 3
Core 17 / 121 / 0 17 / 125 / 0
Development Management 0 / 4 / 0 0 / 4 / 0
Grease Pencil 7 / 275 / 18 7 / 278 / 17
Modeling 44 / 655 / 2 45 / 631 / 4
Nodes & Physics 42 / 749 / 3 35 / 631 / 5
Pipeline & I/O 12 / 189 / 0 12 / 196 / 0
Platforms, Builds, Test & Devices 11 / 82 / 1 11 / 84 / 1
Python API 17 / 198 / 2 17 / 203 / 1
Render & Cycles 61 / 594 / 4 59 / 607 / 5
Sculpt, Paint & Texture 14 / 396 / 6 9 / 350 / 4
User Interface 120 / 883 / 4 107 / 784 / 3
VFX & Video 11 / 208 / 0 11 / 206 / 1
Viewport & EEVEE 61 / 693 / 7 60 / 715 / 12
2.12.2024

Open Low Severity bugs as of 2024-12-02:

Open Normal Severity bugs as of 2024-12-02:

Open High Severity bugs as of 2024-12-02:

31.12.2024

Open Low Severity bugs as of 2024-12-31:

Open Normal Severity bugs as of 2024-12-31:

Open High Severity bugs as of 2024-12-31:

13 Likes
3

Open bugs per module (Low / Normal / High severity):

Module 2.12.2024 31.12 31.1
Platforms, Builds, Test & Devices 11 / 82 / 1

The platform module has not been allocated any resources and as such won’t participate in this project (hence it being missing from the announcement post)

2 Likes
4

Indeed, thank you for adding this clarification.
Hopefully we get more ressources for it in the next year!

1 Like
5

Firstly great thanks for the quality project, much needed, hopefully this will aid some bugs and provide more stability.

It may not be the right thread to ask, but what happens to open (& confirmed) issues of core addons in the old deprecated blender-addons repo? Take fbx for example, has 74 open ones which don’t count into the above mentioned statistic for Pipeline & I/O.
Will those get revisited during the quality project as well or should issues be recreated by their authors in the blender repo?

6

It’s a good place to ask, thank you for your comment. @sergey or @ThomasDinges have we discussed this topic before?

1 Like
7

FBX tasks should be moved (or rather re-created, with link to original report) in blender repo tracker yes. Would be a good opportunity to recheck them too. And same for other add-ons that were moved into addons_core.

3 Likes
8

Not sure why this isn’t just presented as the plan. Because it is!

9

Last UI module meeting we worked out a rough plan for the code quality project, we want to focus on bringing the vast amount of UI tasks under more control: UI Module Quality Project - HackMD

5 Likes
10

After one month, I updated the numbers.

Congrats to:

  • Modeling for closing 24 normal reports
  • Nodes & Physics for closing 118 normal reports
  • Sculpt, Paint & Texture for closing 46 normal reports
  • User Interface for closing 99 normal reports

The remaining participating modules did not change significantly or numbers went up.

11 Likes
11

Great to see the updated number.

Sorry for asking, but when you say closing, it means solved, false positives, repeated or what? :confused:

12

All of these… can be re-checking old reports that are no more relevant, actually checking reports and decide that they are not bugs, and of course fix real bugs :wink:

2 Likes
13

Something I noticed (that unfortunately probably can’t be changed for old data) - the queries & numbers include both “To Do” and “Design” labeled items. IMO both should be removed or otherwise counted separately if we specifically label these as “bugs”.

1 Like
14

I feel like “not bug, closed report”, “very old report, not relevant”, or even “known issue, closing report” wouldn’t be counted as “the goal is to get more fixes in, for a more stable Blender”.

…as those types = nothing was fixed/changed?

2 Likes
15

Having a reasonably clean and up-to-date tracker is part of general quality of a project, as it helps identifying and addressing actual issues more efficiently. And in any case, if one wants to fix a bug, they first need to check that it is (still) actually something that needs to be fixed, which is usually a non-trivial part of the bug fixing activity.

So IMHO it totally makes sense to count them as part of the metrics for the winter of quality.

5 Likes