Re: [Bf-committers] Changes to the Blender.Git submodule configuration

Hi, There is some feedback loop which I've missed yesterday. The new version of the `make update` is needed to bring the repository to the proper state. So, `git pull` (or other means of updating your working branch) is needed to grab the new version of the `make update` script. Best regards, - S

[Bf-committers] Changes to the Blender.Git submodule configuration

Hi everyone, A quick announcement about the changes in the submodule organization of the blender.git repository. It affects both blender-v3.5-release and main branches. In order to resolve the confusion about submodule hashes we are completely removing submodules. The locales and developers tools

[Bf-committers] Discontinuing git.blender.org

Hi everyone, Just a brief announcement that on March 1 we plan to discontinue the git.blender.org domain. Since the migration to Gitea on projects.blender.org the git.blender.org is no longer used to provide the actual sources and is marked to be in the archive/read-only mode. Please make sure y

[Bf-committers] Migration to Gitea is about to start!

Hi everyone, Just a quick note that the migration process from Phabricator to Gita is planned to start at 10:00 CET time (in about 20 minutes). The infrastructure will be set to read-only mode for SVN, Git, and developer.blender.org. Bigger intermittent disruptions are possible. We will keep you

[Bf-committers] Task force: Mark non-trivial DNA as such for C++

Hi everyone, With more parts of Blender moving to C++ some of the shortcomings of old-style DNA structures started to become a bit of annoyance for on-going development (compiler warnings, not-so-semanticly-obvious code, ...). Me and Jacques did some ground work to make operations on DNA structur

Re: [Bf-committers] Proposal for clarified VFX Reference Platform Support

Hi Brecht, Sure there are trade-offs and different ways of solving problems. It is more of what the Blender project considers important. For example: is it more important to spend developers' time on patching our own version (effectively, fork) of Python, or deviate from the Platform by updating t

Re: [Bf-committers] Bf-committers Digest, Vol 1040, Issue 1

Hi Brian, Thanks for sharing the insights. I've almost missed your reply. We have a dedicated mailing list thread for it. The bright side of supporting newer early Python is that the moment VFX Platform releases its new version for the next year all the work is already done and even tested! :) W

Re: [Bf-committers] Proposal for clarified VFX Reference Platform Support

Hi, Jason, taking the LTS release schedule, Python/other libraries release schedule, and VFX platform release schedule, I am not really sure how to achieve this in practice. Not even sure it brings more solutions than problems. Ray, our paths might be different but the goal is the same: minimize

Re: [Bf-committers] Proposal for clarified VFX Reference Platform Support

Hi everyone, I had a discussion with Brecht here. He brought up a good point which I do agree with him is important: keep render engines working. We do have an official render engine API, and breaking render engines support without good reason is not very nice. Here is an update of my proposal:

Re: [Bf-committers] Proposal for clarified VFX Reference Platform Support

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 o

Re: [Bf-committers] Proposal for clarified VFX Reference Platform Support

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 iss

[Bf-committers] Proposal for clarified VFX Reference Platform Support

Hi everyone, This message is meant to address some ongoing confusion about how Blender is adhering to the VFX Reference Platform, and clarify the Blender project’s goals. Currently developers and platform maintainers are spending considerable amount of time in discussions when a library update is

[Bf-committers] Let's Encrypt SSL certificates incident on the blender.org servers

Hi, Just a quick memo about the issue of expired Let's Encrypt certificates. It might be useful for developers who experience issues with HTTPS connection to our servers. One of the root Let's Encrypt certificates did expire today which affected parts of our development infrastructure. In all cas

[Bf-committers] Blender developer week notes - 2021.08.02

Hello everyone, There are no announcements for this week of development. The complete report with modules and projects updates, links and images read it on: https://devtalk.blender.org/t/2-august-2021/19781 Best regards, - Sergey - -

[Bf-committers] Blender developer week notes - 2021.07.26

Hello everyone, Here are the compiled notes for this week's development. For the complete report with modules and projects updates, links and images read it on: https://devtalk.blender.org/t/26-july-2021/19713 Announcements = The comments section [1] of the style-guide document has b

Re: [Bf-committers] Harmonious collaboration - reverting commit process

committers@blender.org> wrote: > > > A common reason why I revert commits is that submodules were changed by > > mistake. Is reverting a good solution? Perhaps worth mentioning. > > > > Jeroen > > > > > > On Wed, Jun 9, 2021 at 12:55 PM Sergey Shar

[Bf-committers] Harmonious collaboration - reverting commit process

Hi, Today I continued to update the development process guidelines and policies on the Wiki. This is based on previous discussions with the other bf-admins, and I'm working with Dalai on the final text adjustments. So today we handled the "polemic" topic of reverting commits: https://wiki.blender.

Re: [Bf-committers] Simple steps to get an harmonious collaboration

h description" rule and it wouldn't > even look out of place. > > --Ray > > [1] > https://wiki.blender.org/wiki/Process/Contributing_Code#Ingredients_of_a_Patch > [2] https://wiki.blender.org/wiki/Style_Guide/Commit_Messages > > > On 2021-06-01 5:05 a.m., Sergey Sh

[Bf-committers] Simple steps to get an harmonious collaboration

Hi, Just a quick note. The bf-admin team worked on several process related documents to ensure a pleasant and efficient development process. Today we've updated wiki with the patch review process: https://wiki.blender.org/wiki/Process/Patch_Review Feedback is welcome. Best regards, - Sergey - -

[Bf-committers] Deprecation of Phabricator

Hi, Just wanted to let everyone know that today Phacility announced that development of Phabricator is phasing out [1] [2]. This does not affect the Blender project immediately, but we need to find a solution to the situation (be it a fork of Phabricator, or be it a migration to some other platfo

[Bf-committers] Code quality day changes

Hi everyone, We have been doing the quality day for a few months already. The idea was to motivate and facilitate all the modules to solve technical debts in their code. Unfortunately, this didn't quite work that great. While there were some nice improvements in localized areas, it didn't work out

[Bf-committers] Code Quality Day - 5/March

Hi, This Friday we have February's code quality day [1]. For the Clang-Tidy project we'll come up with a decision on which warnings we still want to address and support. ANd I would really like to see the WIP patches to be either finished or officially stated that we do not want to address the wa

[Bf-committers] Clang-Tidy: Request for Feedback

Hi, During the past months we seem to cover the majority of the warnings from Clang-Tidy [1]. The remaining onbes either require a newer Clang-Tidy version, or have a patch, or are a bit controversial than it originally looked. I would say we have reached the point where we can declare the Clang-T

[Bf-committers] Code Quality Day - 5/Feb

Hi, This Friday we have February's code quality day [1]. The full list of approved projects for the quality day is combined in a dedicated task [2]. There are few remaining warnings from Clang-Tidy to be addressed for code modernization [3]. Is time for us to look into how to make Clang-Tidy to

[Bf-committers] Code Quality Day - 4/Dec

Hi, This Friday we have December's code quality day [1]. The full list of approved projects for the quality day is combined in a dedicated task [2]. Last day we finished what one might consider essential Clang-Tidy integration warnings. There are now modernize category warnings enabled, which he

Re: [Bf-committers] Support for 32-bit architectures

Hi, I think Sybren will bring some points here, so I will try not to interfere with those to not create too much noise here. One thing which I am missing here is what is the recovery checklist? Mistakes do happen, how can they be efficiently addressed/resolved? Regards, -Sergey- ---

Re: [Bf-committers] Code Quality Day - 6/Nov

Hi, Thought to give a quick update of what happened today. - A lot of all-around cleanup From Campbell - Jacques continued working on moving Blend I/O to IDType - Sergey did various Clang-Tidy warnings - Sybren looked into using Blender's C++ container types in Alembic/USD. Turned out to be more

[Bf-committers] Code Quality Day - 6/Nov

Hi, This Friday we have November's code quality day [1]. The current progress is nicely written up by Dalai in the blog post [2]. The full list of approved projects for the quality day is combined in a dedicated task [3]. Smaller and isolated projects are to tackle Clang-Tidy [4]. We need to wra

[Bf-committers] Code Quality Day - 4/Sept

Hi, This Friday we have September's code quality day [1]. The purpose of this day is to solve long-standing technical debt, and to deploy new techniques and tools to help our work as developers. Over time these practices should naturally be incorporated in the day-to-day code. But the old code is

[Bf-committers] Code Quality Day - 7/Aug

Hi, This Friday we have August's code quality day [1]. The purpose of this day is to solve long-standing technical debt, and to deploy new techniques and tools to help our work as developers. Over time these practices should naturally be incorporated in the day-to-day code. But the old code is ni

[Bf-committers] C++ standard has been upgraded to C++17

Hi, The C++ standard used by Blender has been raised to C++17. This allows developers to use newly introduced features in the language [1]. We are still compliant with the VFX platforms, since there are no binary plugins in Blender, and the precompiled external libraries will not go above C++14.

[Bf-committers] Buildbot is updated is out of maintenance!

Hi everyone, Just a quick note that after a few days of work the Buildbot is considered to be back to regular business! So what did change? All the workers which are compiling latest Git sources are now at the latest available toolchains for their platforms. This allows us to process further with