On 3/23/11 2:13 PM, Robert Leverington wrote:
On 2011-03-23, Neil Kandalgaonkar wrote:
On 3/22/11 6:05 PM, Rob Lanphier wrote:
Our code review tool is pretty nice, but we
can't let it
be the tail that wags the dog.
At the risk of being impolite -- our code review tool is not that nice.
(I don't expect that anyone who worked on it would even disagree with me
here.)
It happens to be our home grown tool, and it uses a framework that more
of us are familiar with. But it's not such an overwhelming asset that we
should consider staying on SVN because of it. In 2011 there are lots of
code review frameworks out there to choose from.
There's nothing stopping a Git backend being created for the code review
extension.
Perhaps I was unclear. My point was that I personally would like to
*not* use our current code review system.
By that I mean both the general paradigm we have, and the tools we are
using.
I'm asserting that:
- There are other software frameworks for code review with more and
better features.
- There are other code review paradigms that are better for team health,
other than "let's spend several months on the backlog every time we want
to release".
--
Neil Kandalgaonkar (| <neilk(a)wikimedia.org>