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

Links

Attendees

Topics

  • Announcements

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

    • Have meetings consistently every two weeks (no matter Philipps availability), no conclusion on how to organize this yet
    • Ideas for ways to include “Bug Fixes” from older releases in the release notes
      • We developed a script to assist with this, sorted some commits, and add a list of bug fixes to the 4.3 release notes.
      • To assist the script for future releases, we are encouraged to fill out the broken and working fields accurately. We are also encouraged to check:
        • The current release, previous release, and all active LTS releases to fill out this information accurately. This can also help with figuring out what should be backported to LTS releases.
      • The next step is to get the script into the Blender repository. Alaska will make a few minor adjustments and open a pull request for this.
      • To reduce stress close to release manually sorting commits that didn’t have the right information, we may run the script on a weekly or bi-weekly basis.
    • Feedback regarding our triaging infrastructure
      • news?
    • Wizard
    • 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?
    • @Sean-Kim proposes to add “Crash” / “Regression” labels
      • news?
    • discussion about exposing dependency cycles to the end user (an idea we have discussed in previous meetings)
      • news?

Meeting Notes

  • Ideas for ways to include “Bug Fixes” from older releases in the release notes
    • Alaska will work on this a bit more and can hopefully open a PR to put this in the release tools soon.
  • There has been progress on the crash window pull request
  • Yimming will discuss exposing dependency cycles in the UI with other developers and create a design task for it.
  • Proposal to add “Crash” / “Regression” labels
    • We didn’t ask other developers for their input. Alaska will try and do this before the next meeting. (a devtalk thread might make sense)

Following meeting

The following meeting will be on 2024-12-19T12:00:00Z. Again it will be open for everybody who’s interested.

3 Likes