Problem: User documentation is lagging behind, yesterday there were quite some open todos for 4.3
Solution: Enforce our committing policy as noted in the developer handbook:
“Document new features and changes in the release notes, either before or directly after committing a feature.” (Source)
“Add a link to the git commit or pull requests at the end of each feature.” AND “Whenever possible, link to the manual entry where to read more about the feature.” (Source)
Proposal: Developers have to add release notes / documentation before or directly after committing a feature. They can ask Aaron or the community for help with that but are responsible that it gets done in time.
Conclusions: just follow the proposal
Fiona and Sergey will find a way to communicate this
Empower Aaron and Pablo to poke developers early
Responsibility of module owner to ensure things land according to the ideal process
Platform Module - Library support
Ray Molenkamp wrote a proposal to formalize the handling of libraries.
Mostly a guideline for the platform module itself, but
Do admins want to have a word in which (new) libs are being added to Blender? (Implications on binary size etc).
Conclusions: Proposal is generally fine.
Thomas will work with Ray to finalize the details.
Follow-ups
Previously:
Sergey will communicate to maintainers of non-supported platforms that they will no longer be officially supported.
Add a code in Blender to hide or inform about unsupported wheels (Campbell).