Are there solutions / best practices for dealing with the Version Management Problem when working on larger blender Projects?
Explanation: Version management means to keep track of who did what, when and why. Blender is a huge GUI driven application, but the work done in blender is typically comparable in complexity with the task of developing software. In such a setup, it is no longer possible to keep track of changes just by looking into the GUI. To be able to work effectively, we need tool support to answer the mentioned questions on a daily basis.
- are there better solutions available than just checking in the blend file as a binary blob into some SCM system (Git, Mercurial, SVN, ...)?
- maybe there are specific filters or exporters available which allow to transform the blend files into something which can be version managed with the tools known from software development?
- branching and merging: are there tools or known methods to integrate changes done by different people working in a team on a common project, but possibly on different branches or development lines?
Of course binary diffs in images and video footage are also relevant, but there isn't much to be done with these, beyond just noting that you're using a new version of some externally linked binary media.