2025-02-06 Triaging Module Meeting

Meetings
1

Biweekly Triaging module meeting for planning and coordination.
Folks on the payroll should attend if possible, others are invited as well.
In these meetings, we can keep us up-to-date on everything triaging, discuss recent important issues and see if we can bring the module forward.
I believe it is also good to see human faces once in a while :), so there is always room for some personal stuff if appropriate.

The meeting will be on 2025-02-06T12:00:00Z. It is open for everybody interested to join the video call (link below).

Links

Attendees

Topics

  • Announcements
    None

  • Winter of Quality came to an end last Friday

    • What did the module achieve?
    • How was the quality project? Did things go according to plan?
    • If there is another quality project, then would you want anything changed?
    • Involvement of triaging team in other modules
"Pending TODOs/followups (wont get an active topic if no news have to be announced"

Meeting Notes

  • Winter of Quality came to an end last Friday

    • What did the module achieve?

      • The triaging module didn’t have a plan for the Winter of Quality project. Most members of the triaging team instead helped out with other modules during the quality project when they were done with triaging for that day.
      • TODO Maybe each triaging member can add their thoughts from their experience with other modules?

    • Involvement of triaging team in other modules

      • Alaska helped writing tests for Cycles
      • Yiming involved in GP module
      • Pratik helped GP and UI

  • Pending TODOs/followups

    • Alaska has made a tool to automatically notify people of old Needs information from user reports: Issues - needs-information-reports - Blender Projects
      • So far Pratik finds this useful.
      • Alaska plans to make further adjustments to this and add every triager to this script.
    • Updates on revisiting “bottom 50” (at least) Needs Triage reports
      • Pratik has looked into roughly 10 of these (88 open reports at the time of meeting). A lot of them are on Needs triage because we’re missing specific hardware to access this.
    • With the release of better open source Large Language Models, Mano is interested in using them instead of OpenAI.
      • We don’t have much details to share on that as they weren’t able to attend the meeting.
    • Feedback regarding our triaging infrastructure
      • We use a script to help write our weekly reports. There have been a few issues with it’s output recently (E.g. Duplicate data, missing data from PRs merged by others)
        • Yimming was planning to look into this
    • Ideas for ways to include “Bug Fixes” from older releases in the release notes
    • discussion about exposing dependency cycles to the end user (an idea we have discussed in previous meetings)
      • Yimming has been experimenting with the OOPS tool in Blender 2.4 to help figure out some design choices for this “exposing dependcy cycles to the end user” idea. For example the OOPS window can get quite crowded with links in complex scenes.
      • Yimming is suggesting adding tabs to the info editor to help expose error messages related to dependency cycles to the user.
      • Pratik: Exposing info about dependency cycle in UI would be useful. So far these logs are printed in system console. On Linux/Mac, user cannot open terminal from blender UI like Windows.
2 Likes
2

@ChengduLittleA An old idea here was to make the info editor have multiple modes. So there wouldn’t only be operators, but there could also be depsgraph, render, viewport, memory usage, etc.

4 Likes