2024-08-13 Blender Admins Meeting

Meetings
1

Attendees

  • Bastien Montagne
  • Campbell Barton
  • Dalai Felinto
  • Fiona Cohen
  • Sergey Sharybin
  • Thomas Dinges

Notes

  • Enum naming conventions
    • Move forward with Brecht’s proposal.
    • Campbell will move it to the official guidelines.
    • Cleanup happen later, although a lot of code already follow the convention.
  • Deprecate and Remove Big-Endian Support
    • No decision was made regarding stop supporting these files.
    • Campbell will add regression tests to the Git LFS (at the moment big-ending support is getting on the way of refactors in the read code).
  • Limit supported architectures to x64, arm64
    • Communicate to the maintainers (easy, just poke @here in blender-builds)
    • Need to go to blender.org page somewhere (Thomas can help with this)
  • Down-casting, static_cast and dynamic_cast usages
  • Module separation VFX & Video module in: Compositor, VSE, Tracking
    • This is an old topic, but it become more pressing recently since both Compositor and VSE are active with different members and separate meetings.
    • There are a few proposals regarding other module:
      • Fiona: Just do it, and make it a case of other modules.
      • Dalai: Use meeting as a criteria for separation.
    • For this particular module this is the proposed course of action:
      • VFX Module - umbrella module (similar to the Render module)
        • Compositor - module
        • VSE - module
        • Tracking - module, maintenance-only mode
    • Sergey will check with the triaging team if there are other considerations, otherwise he will just move on with the changes.
  • New Triaging Process
    • Do the non-controversial changes.
    • Known Issues
      • No decision regarding whether or not to archive them.
      • Part of the issue is that it is not trivial now to find open or closed issues in gitea.
      • Sergey will do a follow up to try persuading Bastien on the merits of archiving them and possible solutions.
  • Blender 4.2 cycle
    • Late merge of big features like Extensions and EEVEE-Next caused lots of feature work during Beta, rather than focusing on bug fixes.
    • High Priority bugs were not handled well or issues were tolerated for release.
    • Suggestion:
      • Stop doing exceptions and enforce the following two rules:
        • Bigger features must be merged at the beginning of Alpha and can only be polished throughout Alpha. No more feature improvements in Beta.
        • High Priority reports must be handled before feature development.
      • Clear communication (a note in the description) that mentions whether the task in on a vendor side.
      • Assign milestones as much as possible, in particular for high severity issues.
      • Only tackle bigger refactors only as part of a project.
  • Bloom: Bring back the 4.1 Bloom functionality for EEVEE
    • Now that the 4.2 release is out, this topic is back on the agenda.
    • On a hindsight it shouldn’t have been removed as it was, but it was caught too late into development.
    • Dalai is working on this topic with Clément and Omar to see how we can tackle this #126277

Follow ups:

  • Campbell will move the Enum Naming convention to the official guidelines.
  • Campbell will add Big-Endian files regression tests to the Git LFS.
  • Sergey will communicate maintainers of non-supported platforms that they will no longer be officially supported.
  • Thomas will update blender.org requirements page regarding supported architectures.
  • Sergey will ask Jacques to put the down-casting proposal into the guidelines.
  • Sergey and Bastien will talk about archiving Known Issues.
  • Sergey will check with the triaging team regarding splitting the VFX & Video module.
  • Sergey will send an email to admins about LTS rotation.
7 Likes