changed 12 days ago
Linked with GitHub

Attendees

  • Philipp
  • Pratik
  • Yimming
  • Alaska

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
    • 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?
    • 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.
    • 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.

Meeting Notes

  • Ideas for ways to include "Bug Fixes" from older releases in the release notes
  • Discussion about Tests:
    • Are docs sufficient for any dev to add a test in lets say 30mins?
    • Which scenarios are complicated/hard adding tests for?
      • some are easier (e.g. Cycles just add a .blend, generate the expected output image, commit those)
      • we have mesh equality API, but not for other types
      • UI (mouse input possible?)
  • followup on the VR report with Jeroen
Select a repo