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

Links

Attendees

Topics

Meeting Notes

  • Announcements

    • Pratik will become co-owner of the Triaging module
      • This is to split up the responsibilities of the Triaging module between people.
      • Reasons for doing this include:
        • Philipp can be unavaliable when working on LTS releases or for other personal reasons.
        • Philipp and Pratik are in fairly different time zones, so this means a head of triaging will be avaliable more of the time.
    • “End of the Year” , recap.
      • As the triaging module we have:
        • Improved the issue template
        • Improved documentation for some users making new bug reports
      • Statistics:
        • There were roughly 20-30 reports per day, roughly 10000 in 2024
        • There are roughly 11 fix commits per day, roughly 3750 in 2024
        • Throughout 2024, members of the triaging module contributed roughly 650 fix commits [~107 per Triaging member as opposed to ~160 per member of other modules].
        • In addition, roughly 10 reports per day are closed by the Triaging team (Primarily by determining it’s not a bug,)
        • This does mean that some reports may stay open for a long time
  • Pending TODOs/followups

    • Ideas for ways to include “Bug Fixes” from older releases in the release notes
    • Proposal to add “Crash” / “Regression” labels
      • We asked Sean if they still wanted these labels. They said they would think about it and get back to us at a later date.
      • If Sean decides they want these labels, then we’d ask for input form other developer’s and make a decision then.

Following meeting

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

8 Likes