[Bf-committers] Cycles-Baking - 1st round of code review

[Jonas Wielicki]

Disclaimer: I have not looked at the code, nor am I a blender dev.

On 23.03.2014 13:28, Antony Riakiotakis wrote:
> I am not really sure this is important for features in development. At that
> point it's usually meaningless to talk about which commit 'broke'
> something, because that something does not even exist to be tested upon.

In my humble opinion, this is only correct in an ideal world. In the
real world, even new features sometimes introduce unexpected side
effects (memory corruption for example).

> For this to maybe work you have to do things correctly right from the
> start. But coders usually try things out and then commit. In practice
> development itself is rarely linear. You may 'finish' a certain part of the
> code only to find later that it may be broken so you refactor, etc. While
> this would be nice to have I don't see how this would work in practice with
> unfinished features.
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>