Triaging Module Meeting
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-07-18T11: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 chat channel
- live meeting notes
Attendees
Topics
-
number of untriaged reports is high (esp. following the 4.2 release), should take priority over everything else for the time being
-
Philipp has a week off from 29.07 through 03.08, does the team need additional help?
-
look for a way to include âBug Fixesâ in the release notes, gather ideas on how to do this best with minimal effort
-
followups from last meeting
- improve upon issues with unavailable hardware
- Triaging module should create a list of hardware specific issues is pending
- 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 pending
- feedback regarding our triaging infrastructure
- Proposal to add more labels: Discussion around adjustments to Blender issue labels
- maybe mention the âUnconfirmedâ label there as well (along with the consequences it had back in the days of phabricator), decide upon actions to take next meeting if Alaska is attending
- for the release process: do we need a ârelease showstopperâ label? (the corresponding milestone is not sufficient) â probably something for * @ThomasDinges and * @lichtwerk to decide
- Quality Project
- recap: only partial success
- Check on the possibility of auto-changing the label back from âNeeds Info from Userâ to âNeeds Triageâ if there is a response: progress?
- Similar to Thomasâ daily high priortiy bug list: drop a list of these in our Triaging channel? progress?
- Bug reports on Extensions:
- clarify current situation
- improve upon issues with unavailable hardware
-
recent important issues that are somehow hard to triage
- if time permits, go over specific issues
Meeting Notes
-
4.2
- Lots of EEVEE crashes with older AMD cards > just ping devs/Richard
in the report if we cant repro
- Lots of EEVEE crashes with older AMD cards > just ping devs/Richard
-
Philippâs week OFF: decide if we want someone to help out with triaging while they are away. See if this decision can be made short term, if so, make this decision next week after seeing how the work load reduces as Blender 4.2 gets older.
-
Ideas for ways to include âBug Fixesâ from older releases in the release notes.
- We would ideally want it to be automated. We discussed a few ideas. Further ideas are welcome.
- Automatically check the âWorking versionâ field of reports to see if the issue was introduce in the current version, or was in older versions (Most users donât provide this information)
- Automatically check the âBrokenâ field of reports to see if the issue was reported from a older version.
- Filter reports attached to âfixâ commits based on the date the report was made. We will miss reports for old versions made during the development of a new version.
- Cherry picking fixes from new versions onto older versions and check for merge failures (Will not work in some cases, such as a bug fix after a refactor, or will give a false positive for a bug fix for a bug introduced in a different part of the code)
- We could do manual work. But there is a high possibility for people to miss it.
- Triagers add a label that denotes it is a bug from a older version.
- Ask developers to add this information to their commit message?
- We would ideally want it to be automated. We discussed a few ideas. Further ideas are welcome.
-
Followups from last meeting
- improve upon issues with unavailable hardware
- Triaging module should create a list of hardware specific issues. Still pending. Philipp will start 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) - We still need to gather examples.
- Feedback regarding our triaging infrastructure
- #122191 - WIP: Add a script to collect system information when Blender isn't opening - blender - Blender Projects Philipp will review this when they have time.
- #58 - Add guides on how to manually collect bug report system information - blender-developer-docs - Blender Projects Philipp will review this when they have time.
- Proposal to add more labels:
- Proposal to add a âRelease Show Stopper labelâ for bugs that need to be fixed before the next version. We will need to talk to Thomas about this as it primarily effects them.
- This lead to another discussion around using milestones after a version has been released. Philipp will talk to Thomas about this as it primarily effects them.
- Proposal to add a âRelease Show Stopper labelâ for bugs that need to be fixed before the next version. We will need to talk to Thomas about this as it primarily effects them.
- Quality Project
- Recap: Quality project did not go as well as expected.
- Possibility of auto-changing the label back from âNeeds Info from Userâ to âNeeds Triageâ if there is a response.
- At the moment we have decided not to do that and would prefer to do things manually. Primarily because there can be some false positives.
- Similar to Thomasâ daily high priortiy bug list: drop a list of âNeeds infoâ reports in our Triaging channel?
- If we really need a reminder, then we can go with a simple reminder like a weekly âReminder: Check your âNeeds infoâ reportsâ. We can expand to something more technical if needed later on.
- Bug reports on Extensions:
- Get link to external issue tracker in the Blender UI (check with Campbell and Dalai)
- Clarify if dev is responsible to check their issue tracker â related: get link gitea issue tracker in the Blender UI if dev opted out of providing the link (check with Campbell and Dalai)
- Clarify rules of bug reporting (language etc. Add this to the Terms of Service?)
- Philipp will double-check again
- improve upon issues with unavailable hardware
-
Other discussion
- If there is a studio or creator using LTS, and itâs really important to them to have a LTS version that recieves regular bug fix updates, let Philipp know (would be nice to know how much of a âsuccess storyâ LTS really is).
Following meeting
The following meeting will be on 2024-08-08T11:00:00Z. Again it will be open for everybody whoâs interested.