http://www.reddit.com/r/programming/comments/1x66zv/the_rust_repository_closed_the_second_most_number/

This made me wonder what the D stats are? Obviously we don't use github's bug tracker, but I think we still close a lot of issues as FIXED. Can anyone show some D stats?

On Thursday, 6 February 2014 at 21:14:21 UTC, Andrej Mitrovic wrote:
> http://www.reddit.com/r/programming/comments/1x66zv/the_rust_repository_closed_the_second_most_number/
>
> This made me wonder what the D stats are? Obviously we don't use
> github's bug tracker, but I think we still close a lot of issues as
> FIXED. Can anyone show some D stats?

http://dlang.org/bugstats.php

On 2/6/14, 1:16 PM, Namespace wrote:
> On Thursday, 6 February 2014 at 21:14:21 UTC, Andrej Mitrovic wrote:
>> http://www.reddit.com/r/programming/comments/1x66zv/the_rust_repository_closed_the_second_most_number/
>>
>>
>> This made me wonder what the D stats are? Obviously we don't use
>> github's bug tracker, but I think we still close a lot of issues as
>> FIXED. Can anyone show some D stats?
>
> http://dlang.org/bugstats.php

... which is not working properly at the moment. It's PHP code, does anyone have the time to mess with it? I recall Brad Roberts mentioned the problem to me at some point.

Andrei

On 2/6/14, 1:13 PM, Andrej Mitrovic wrote:
> http://www.reddit.com/r/programming/comments/1x66zv/the_rust_repository_closed_the_second_most_number/
>
> This made me wonder what the D stats are? Obviously we don't use
> github's bug tracker, but I think we still close a lot of issues as
> FIXED. Can anyone show some D stats?

One issue we can't quite brag about is the glacial pace of reviewing and accepting already proposed contributions.

Andrei

On Thursday, 6 February 2014 at 21:14:21 UTC, Andrej Mitrovic wrote:
> http://www.reddit.com/r/programming/comments/1x66zv/the_rust_repository_closed_the_second_most_number/
>
> This made me wonder what the D stats are? Obviously we don't use
> github's bug tracker, but I think we still close a lot of issues as
> FIXED. Can anyone show some D stats?

I think this covers it:

https://d.puremagic.com/issues/buglist.cgi?chfieldto=2013-12-31&query_format=advanced&chfield=resolution&chfieldfrom=2013-01-01&chfieldvalue=FIXED&bug_status=RESOLVED&resolution=FIXED

"1356 issues found"

I'm not sure how Github counts "issues closed" because I believe they treat pull requests as issues too so the number could be double what it should probably be (I could be mistaken on that).

Either way, it's impressive work by the Rust team.

On Thursday, 6 February 2014 at 21:19:49 UTC, Andrei Alexandrescu wrote:
> On 2/6/14, 1:13 PM, Andrej Mitrovic wrote:
>> http://www.reddit.com/r/programming/comments/1x66zv/the_rust_repository_closed_the_second_most_number/
>>
>> This made me wonder what the D stats are? Obviously we don't use
>> github's bug tracker, but I think we still close a lot of issues as
>> FIXED. Can anyone show some D stats?
>
> One issue we can't quite brag about is the glacial pace of reviewing and accepting already proposed contributions.
>
> Andrei

One thing I observed is that our bugtracker and "idea collection" in the wiki is not very clear. For example I always search for a list of all open issues at https://d.puremagic.com/issues/ (I now know there is a link on http://dlang.org/bugstats.php) and it took me ages to find the DIP page in the wiki.).

I think an alternative issue/idea tracker in the style of the github issues would be a useful improvement. Mabye even github issues if a hosted solution is an alternative.

On Thursday, 6 February 2014 at 21:50:40 UTC, Brad Anderson wrote:
> I'm not sure how Github counts "issues closed" because I believe they treat pull requests as issues too so the number could be double what it should probably be (I could be mistaken on that).

Likely. In GitHub semantics "pull request" == "issue with attached code".

On Thursday, 6 February 2014 at 21:19:10 UTC, Andrei Alexandrescu wrote:
> On 2/6/14, 1:16 PM, Namespace wrote:
>> On Thursday, 6 February 2014 at 21:14:21 UTC, Andrej Mitrovic wrote:
>>> http://www.reddit.com/r/programming/comments/1x66zv/the_rust_repository_closed_the_second_most_number/
>>>
>>>
>>> This made me wonder what the D stats are? Obviously we don't use
>>> github's bug tracker, but I think we still close a lot of issues as
>>> FIXED. Can anyone show some D stats?
>>
>> http://dlang.org/bugstats.php
>
> ... which is not working properly at the moment. It's PHP code, does anyone have the time to mess with it? I recall Brad Roberts mentioned the problem to me at some point.
>
> Andrei

The problem was that the links were switched to use HTTPS but dlang.org's php installation does not support https.  I tried to provide some guidance for someone that I thought make a pull request to fix it but I guess they never got around to it.[1]

I'll make a quick pull request in a moment.

1. http://forum.dlang.org/post/ohdqneewjzjdeijmkacu@forum.dlang.org

On Thursday, 6 February 2014 at 21:54:59 UTC, Brad Anderson wrote:
> I'll make a quick pull request in a moment.

https://github.com/D-Programming-Language/dlang.org/pull/491

On 2/6/14, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
> One issue we can't quite brag about is the glacial pace of reviewing and accepting already proposed contributions.

There are some pull requests which are explicitly waiting for an approval or feedback by you and/or Walter. Even though people have tried notifying you both I'm pretty sure your notification pages are likely huge, so it's hard to find out what notifications are a priority (the notifications tend to be big enough for me and I even have free time on my hands!).

I've thought about compiling a list of these pulls which are blocked and posting to the NG (with a quick summary for each pull) so both of you can have a quick look when you gather some free time.

Does that sound good to you?