Re: [Discuss-gnuradio] Coverity scan and GNU Radio

[Philip Balister]

On 10/02/2013 01:56 PM, Ben Hilburn wrote:
> If you look at a specific issue, you can edit the meta information about it.
> 
> To avoid multiple people going after the same bug, and then ending up
> having to throw one person's work away, should we take advantage of the
> "Owner" field and have people assign bugs to themselves as soon as they
> start working on it?

Let's try this this for a while and see how it works out.

Philip

> 
> This obviously introduces the risk of people assigning bugs to themselves
> and then never actually completing the task, but that might be better than
> a rush of work that ends up unused. If people only assign a bug to
> themselves once they start actually writing code (i.e., don't claim a bug
> if you plan to work on it in the future), it might help avoid this issue,
> somewhat.
> 
> [image: Inline image 1]
> 
> Thoughts?
> 
> Cheers,
> Ben
> 
> 
> On Wed, Oct 2, 2013 at 10:16 AM, Philip Balister <address@hidden>wrote:
> 
>> We've added GNU Radio to the list of projects on Coverity Scan.
>>
>> Coverity is a static analysis tool that finds many coding mistakes.
>>
>> https://scan.coverity.com/faq
>>
>> If you want to get started contributing to GNU Radio, this is a good
>> place to find some easy tasks. That said, please take some time to look
>> at the bugs and make the proper fix and do not just make changes to
>> silence the messages.
>>
>> When you commit a fix, please reference the Coverity ID (CID) in the
>> commit message. For example:
>>
>>
>> https://github.com/gnuradio/gnuradio/commit/dab30e873a8849712e03c26066909a62c8831880
>>
>> Find the GNURadio project at:
>>
>> https://scan.coverity.com/projects
>>
>> and add yourself to the project to access the analysis. Every Monday,
>> the scan is updated.
>>
>> Philip
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>