On Sat, 4 Jul 2015 20:20:23 +0200 Peter Stuge wrote: > It's important that the review flow is well-understood and efficient.
This is impossible in our case due to the lack of manpower. We already have a lot of bugs, patches, stabilization requests hanging over there for months and even years. Stabilization request will require at least two developers to participate in each commit. This will double manpower required at least. Such approach can kill the whole project. Code review is good at a limited scope, e.g. for non-developers where we have review anyway. And as was already told in this thread, the best is the enemy of the good. In no way we should delay git migration due to possible git review. Best regards, Andrew Savchenko
pgpaeQblTgCEP.pgp
Description: PGP signature
