On Mon, 06 Jul 2015 19:20:14 +0200 hasufell wrote: > On 07/05/2015 08:05 AM, Andrew Savchenko wrote: > > 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. > > > > People misinterpret "manpower". If we successfully switch to a > code-review approach, then we will need _less_ manpower in the sense of > actual gentoo developers.
You're mixing different issues here. Code review process for contributors (outside of development team) will indeed save time and manpower. But code review for each developer commit will kill time and effort undoubtedly, while net quality will have little to negligible improvement. Best regards, Andrew Savchenko
pgp40PFnATWYC.pgp
Description: PGP signature
