Code quality project - Q2 2024

Hello everyone, as part of the planning for this second quarter, we’d like to do a project focused on code quality: that is, tackling more bug reports, some legacy or backlog issues.

This was presented to the internal dev team in April and should be possible as a few people will be done with their current projects (hooray!).

Thus, we need each module to work on a plan:

  • which bug reports should be prioritized. Are there any that require more work/attention?
    • Check on old reports too. Things that are in the tracker for 2+, 5+ years etc. Maybe some things have been fixed already or other code changes make it easier to fix now?
  • are there areas of the code with many bug reports? This should be prioritized.
  • anything that has been postponed for a while? a dream refactor?
  • how good is the test coverage? Are there (enough) tests? Do you have a workflow of adding tests alongside fixes?
  • who can participate: it would be great to have every contributors’ support, of course!

If you want help to pick priorities, please reach out to Sergey. Also, the triaging team may have some pointers :wink:

When:

  • plan for end of May, so other developers can review each others’ plans
  • work on this quality project in June

How to share plan:

  • add ideas here
  • or write a reply in this thread about the plan and add the link to the document

Let me know if you have any question!

20 Likes

That sounds awesome. I am really looking forward to a more bug-free Blender <3

1 Like

Recap of today’s (31/05) meeting with the development team:

Topics

What

  • Main targets: solving bugs, closing issues.
    • Making the code better

How

  • All modules should have a list of priority issues
    Especially: Nodes and Physics, UI, VFX (for VSE), based on the people who’ll be available in June
  • Look at list of issues and prioritize on Issues - blender - Blender Projects
    • Label Type: bug
    • Sort by: oldest
  • Then run through them and solve or close them.

Notes

  • the Quality project for June 2024 is smaller than originally planned due to development projects taking more time.
    → this is okay, we do it as a first step, to get the ball rolling, and improve the process and planning in the next quarters

  • everyone should check the reports that need info from developers

  • documentation is also an area where extra efforts are needed

  • also a whole list of improvements for Animation and Rigging or Modeling, that anyone could pick up - please reach out to Thomas or I to keep us in the loop

  • @julianeisel will focus on UI debug and maintenance with @Harleya , and on Assets refactor

  • @filedescriptor will start getting into VSE area and bugs

8 Likes