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-01-23T12: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
Topics
-
Announcements
- any?
-
Pending TODOs/followups (wont get an active topic if no news have to be announced)
- Ideas for ways to include “Bug Fixes” from older releases in the release notes
- Feedback regarding our triaging infrastructure
- news?
- 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.
- Discussion about Tests:
- reply in devtalk
Meeting Notes
- Announcements
- @lichtwerk will be in Amsterdam Monday through Wednesday next week
- Pending TODOs/followups
- @Alaska has made a tool to automatically notify people of old
Needs information from user
reports. They will set this up for some members of the triaging team and see how it goes. - TODO: go through “bottom 50” (at least) Needs Triage again, they havent seen progress in a while
- TODO: go through “bugfixes for release” script output (and correct the remaining ones in limbo).
- @PratikPB2125 looked at UI module bugs for past few weeks. Noticed wrongly labelled reports there (mostly about gizmo and viewport interaction). Those reports possibly never reached to correct module, left unaddressed for years. This might be just one example. In such case, we could double check in triaging module channel.
Following meeting
The following meeting will be on 2025-02-06T12:00:00Z. Again it will be open for everybody who’s interested.