[LLVMdev] [cfe-dev] llvm.org bug trend

Alex Weisberger alex.m.weisberger at gmail.com
Tue Jul 30 12:08:31 PDT 2013

A bug fix month is certainly not a bad idea. It gives people who want to
contribute a good starting point if they don't know where to begin. I fall
under that category so I would benefit from that. A win-win situation as
they say.
On Jul 30, 2013 2:54 PM, C. Bergström <cbergstrom at pathscale.com> wrote:

> On 07/31/13 01:31 AM, Robinson, Paul wrote:
>> Over most of the past year, I have been keeping an eye on the overall
>> LLVM.org open-bug count.
>> Sampling the count (almost) every Monday morning, it is a consistently
>> non-decreasing number.
>> I thought I’d post something about it to the Dev lists, as the count
>> broke 4000 this past week.
>> For your entertainment here’s a chart that Excel produced from the data.
>> (To make it more
>> dramatic, I carefully did not use a proper zero point on the X-axis.)
>> I do not have per-category breakdowns, sorry, just the raw total.
>> Makes me think more seriously about cruising the bug list for something
>> that looks like
>> I could actually fix it…
>>  More users and more bug reports - I wouldn't be surprised if the hidden
> number of "bugs" was over 10k. Is there a way to get bugs fixed per month
> or per week? Even if that number was decreasing I'd just attribute it to
> llvm/clang stabilizing and things becoming more complicated to fix. By
> comparison how many open issues does gcc currently have. I'm not trying to
> take away from your point, but there's probably not magic bullet.
> Maybe a bug fix month? (Trying to sort out a bunch of low hanging fruit
> that new developers may be able to fix?)
> ______________________________**_________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/**mailman/listinfo/llvmdev<http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130730/e4c3b5ef/attachment.html>

More information about the llvm-dev mailing list