On Thu, Mar 24, 2011 at 7:07 AM, Neil Kandalgaonkar neilk@wikimedia.org wrote:
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.
I don't believe anyone said it had to a home grown solution, but rather, that we needed a soultion that work before any transfer could really take place, Perhaps some of theses CR frameworks could be listed on the git pages on wiki.
On Thu, Mar 24, 2011 at 7:13 AM, Robert Leverington robert@rhl.me.uk wrote:
There's nothing stopping a Git backend being created for the code review extension.
There is a bug for that already in bugzilla!
On Thu, Mar 24, 2011 at 7:19 AM, Neil Kandalgaonkar neilk@wikimedia.org wrote:
- 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".
I'm sure that discussion is always welcome, but perhaps that should be discussed in a non SVN vs <insert (D)VCS of choice> thread. No matter what, we will always end up with a backlog of unreviewed code because so few people people that actually spend their time doing it unless they are dragged over from their projects to do it.