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

Antony Riakiotakis kalast at gmail.com
Sun Mar 23 13:28:54 CET 2014


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.
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.


More information about the Bf-committers mailing list