2025-03-06 Triaging Module Meeting

[lichtwerk]

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-20T12:00:00Z. It is open for everybody interested to join the video call (link below).

Links

• Video call google meet for now, we can try jitsi as well if people prefer
• #module-triaging matrix chat room on chat.blender.org
• #module-triaging matrix chat room link for other matrix clients
• live meeting notes

Attendees

• @Alaska
• @lichtwerk
• @PratikPB2125
• @iss
• @ChengduLittleA

Topics

• Announcements
  • any?

"Pending TODOs/followups (wont get an active topic if no news have to be announced"

• talk about Proposal - Label Changes
• Alaska has made a tool to automatically notify people of old Needs information from user reports: Issues - needs-information-reports - Blender Projects
• Updates on revisiting “bottom 50” (at least) Needs Triage reports
• Ideas for ways to include “Bug Fixes” from older releases in the release notes
  • PR #131615 - Release tools: Add script to generate a list of bugs fixed from last release - blender - Blender Projects has landed, also #135218 - Release tools: Add a option to ignore certain bug reports in list of bug fixes - blender - Blender Projects and Release tools: Refactor bug fixes per release script to be easier to expand · 60e4b0e5d0 - blender - Blender Projects
• 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
• Wizard
  • Gather a list of two or three examples from “out there” that work similar to what we want to achieve (add that to #78 - Gitea: Triaging Wizard - blender-projects-platform - Blender Projects) is still pending, some more discussion in #121260 - Issue template design discussion - blender - Blender Projects though regarding Richards experiments
• Could we add a feature that lets users know the location of crash logs after Blender crashes so they can more easily provide it in a bug report?
  • There has been progress on the crash window pull request
• discussion about exposing dependency cycles to the end user (an idea we have discussed in previous meetings)
  • Yimming will discuss exposing dependency cycles in the UI with other developers and create a design task for it.
    • #134659 - Diagnostics tools within the Info space - blender - Blender Projects
    • WIP PR #134672 - WIP: Info: Adding a page for dependency cycle report on the UI - blender - Blender Projects
• Discussion about Tests:
  • reply in devtalk

Meeting Notes

• Announcements

  • Pratik asked devops about the idea of deloying a LLM on Blender foundation servers for the AI assisted extensions Gerimano has been working on.
    • Devops is currently busy with other things, so it may take some time before we see any movement here.
    • There is still ongoing experimentation wrt.
      • OSS LLMs
      • using Retrieval Augmented Generation on top

• TODOs/followups

  • Ideas for ways to include “Bug Fixes” from older releases in the release notes
    • Alaska added a extra feature to it to allow triagers to ignore reports from the release notes in case they are too hard to track down: #135218 - Release tools: Add a option to ignore certain bug reports in list of bug fixes - blender - Blender Projects
  • Alaska has made a tool to automatically notify people of old Needs information from user reports: Issues - needs-information-reports - Blender Projects
    • The source code is now avaliable, and triagers lists have been consolidated into a single report: #1 - Triagers list of needs info reports - needs-information-reports - Blender Projects
  • Discussion about exposing dependency cycles to the end user
    • Design task: #134659 - Diagnostics tools within the Info space - blender - Blender Projects
    • PR: #134672 - WIP: Info: Adding a page for dependency cycle report on the UI - blender - Blender Projects
    • Yimming has been making some progress on this.
    • The idea was proposed to maybe give a dependency cycle warning in the viewport to make it easier to see.
    • One issue with the dependency cycle information in it’s current form is it can be hard for some users to track down the culprit objects based on the information shown.
      • Maybe a button could be added to info editor that automatically selects objects in a dependency cycle.
      • Even with this button, users may have a hard time tracking the exact cause (E.g. A specific property on a modifier is causing a issue). So if possible, could the button automatically switch to the offending property?
    • The current proposed plan is to start with something simple, get that landed into main, then proceed from there with extra features.

Following meeting

The following meeting will be on 2025-03-20T12:00:00Z. Again it will be open for everybody who’s interested.