Re: GOP-PROP 13: patch management tools

[Carl Sorensen]

On 9/21/11 9:25 PM, "Colin Campbell" <address@hidden> wrote:

> On 11-09-21 04:13 PM, Graham Percival wrote:
>> On Tue, Sep 20, 2011 at 09:04:39PM +0200, Janek Warchoł wrote:
>> 
>>> One thing comes to my mind: there is some code revieving tool on
>>> Google Code.  I remember that i saw it being used in some other
>>> project.  It's a bit hidden, but i managed to found some info:
>>> http://code.google.com/p/support/wiki/CodeReviews
>>> Looks that we need to add our source code to the Google Code to be
>>> able to use that.
>>> I think this may be worth considering.  Could we add our source to
>>> Google Code and see what we can do then?
>> Of course it's worth considering, but I don't see that cutting
>> down on the duplicate discussions.
>> 
> 
> I'm solidly with Janek here, Graham.  As it sits, a person wanting to
> follow the trail of a (bug/issue/enhancement request) has to find the
> thing on two separate web-sites, where developers log in despite your
> comment above, using two different tracking numbers and possibly two
> different descriptions.  The curious person also has to read -devel and
> -bug to be sure nothing relevant was sent mail-list only.  No doubt it
> would be a wrench converting to a code management system, but I firmly
> believe the benefits from having all relevant material, discussions,
> patches and reviews, in a single place, are immediately large, and that
> although there is no way to quantify it  but one can reasonably expect
> it, a synergy will develop where unexpected things happen as a result of
> seeing a bigger picture.

>From my initial exploration of Code Review on Google Code, I don't see any
way to make an automatic linkage from a code review request to an issue.  In
fact, a code review request makes a new issue...

Oh, wait, I guess we could link the code review request to the issue(s) that
generated the patch, so maybe the linkage is possible.

I'll try it on my sandbox.

Thanks,

Carl