The general guideline will be to keep Blender functionally compatible with 2.8x and later. Existing workflows or usability habits shouldn’t be broken without good reasons – with general agreement and clearly communicated in advance.īefore 3.0 gets released, all module teams will check on reviewing ongoing implementation and workflows, and come with design docs with requirements, outlining what we accept to be revised, and what we stay away from now. The module teams should make clear which changes will be happening, what the user benefits are, how we will keep compatibility of previously saved work, and (last but not least) how to get involved as a contributor. Most areas in Blender are quite stable, but in some areas bigger changes are being expected: for physics, ‘everything nodes’, sculpting/painting, texturing, and character rigging. None of these changes will be violating the roadmap as outlined for 2.8 though. The core module will be empowered to manage code standards and engineering practices everywhere in the Blender code more strictly (please write docs and provide tests!).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |