Hi all,
Here are the compiled notes for this week's development. For the complete
report with modules and projects updates, links and more read it on:
https://devtalk.blender.org/t/17-january-2022/22308
Welcomes
* Henrik Dick (author of complex solidify modifier), has been granted
You may feel like you're alone in this, however you may
have an ally in me, and I may even go further than you.
If you read my previous emails in this thread carefully
you'll notice I have personally made no call regarding
the python version, I Don't feel it's my place to make
that call, I'm not
For reference there is more discussion about this in the two tasks:
2021: https://developer.blender.org/T83246
2020: https://developer.blender.org/T68774
My preference is still to track the full VFX platform, including the Python
version. However I know I'm in the minority on this, and I'm not
> I don't really feel great about Python
> being the only exception allowed to be digressed
> from the platform.
I think you're misunderstanding the VFX Platform goals,
it has nothing to do with asset compatibility throughout
the pipeline. Otherwise, it would specify what formats
would have to be
Hi Bastien,
That's a good question you're bringing.
For the Python my thoughts are aligned with Campbell.
For other libraries I wouldn't make it an official support in the terms
that it is us who verifies Blender compiles and works with library versions
we don't use ourselves, but we should be
On Mon, Jan 17, 2022 at 11:12 PM Bastien Montagne via Bf-committers
wrote:
>
> Hi Sergey and all, and thanks for this proposition.
>
> This proposal makes complete sense to me. I do not see any benefit for
> Blender to stick to a strict compatibility with VFX platform, but indeed
> ensuring a
Hi Sergey and all, and thanks for this proposition.
This proposal makes complete sense to me. I do not see any benefit for
Blender to stick to a strict compatibility with VFX platform, but indeed
ensuring a file-level compatibility seems a good minimum guaranty.
I have one question though,
On Mon, Jan 17, 2022 at 9:24 PM Sergey Sharybin via Bf-committers
> I agree that the outcome should be much more prominently communicated.
> That's what I think should happen as an outcome of discussion in this
> thread: we come up with policy and explicitly communicate it.
+1, just noting that
Sergey, the correct link to Campbell's reply would be:
https://lists.blender.org/pipermail/bf-committers/2021-May/050998.html (it
was missing .html in his original email)
Op ma 17 jan. 2022 om 11:24 schreef Sergey Sharybin via Bf-committers <
bf-committers@blender.org>:
> Hi,
>
> Thanks for the
Hi,
Thanks for the feedback.
I don't really feel great about Python being the only exception allowed to
be digressed from the platform. It is the most impactful library from the
ones which are directly facing users. If we allow it to be different from
what the Platform is stating, I don't see
10 matches
Mail list logo
