www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - D Bugzilla is still the right place to report problems

reply user1234 <user1234 12.de> writes:
With all what's going on, I wanted to remind you that. In case 
you want it to be ever fixed. Roger this ?

https://issues.dlang.org/
Jan 15
next sibling parent Dennis <dkorpel gmail.com> writes:
On Tuesday, 16 January 2024 at 00:32:13 UTC, user1234 wrote:
 With all what's going on, I wanted to remind you that. In case 
 you want it to be ever fixed. Roger this ?

 https://issues.dlang.org/
Indeed! A few days ago I found a message on Discord about how std.mmfile is underdocumented. I put it in bugzilla and fixed it: https://github.com/dlang/phobos/pull/8891 But I don't keep up with Discord messages, I just happened to read that. I probably missed many other easy to fix issues posted somewhere else than bugzilla. If you can't create a bugzilla account (while we're still transitioning to using GitHub issues), you can post it somewhere else, but notify the issue managers (Razvan and I). You can ping me dkorpel on GitHub and Discord.
Jan 16
prev sibling parent reply Andrea Fontana <nospam example.org> writes:
On Tuesday, 16 January 2024 at 00:32:13 UTC, user1234 wrote:
 With all what's going on, I wanted to remind you that. In case 
 you want it to be ever fixed. Roger this ?

 https://issues.dlang.org/
I still don't get why we're not using github for issues in 2024. Andrea
Jan 16
next sibling parent reply Siarhei Siamashka <siarhei.siamashka gmail.com> writes:
On Tuesday, 16 January 2024 at 13:27:14 UTC, Andrea Fontana wrote:
 On Tuesday, 16 January 2024 at 00:32:13 UTC, user1234 wrote:
 With all what's going on, I wanted to remind you that. In case 
 you want it to be ever fixed. Roger this ?

 https://issues.dlang.org/
I still don't get why we're not using github for issues in 2024.
An argument against this is that in the long run github may eventually deteriorate or go belly up. And this is a risk. Similar to what happened to the sourceforge.net platform. The git source repository can be easily mirrored anywhere else. But the issue tracker is a pain to migrate. The main problem with https://issues.dlang.org/ is that gmail accounts are (or were?) banned there. After roughly a year of waiting for the "imminent" migration to github, I just ended up registering a throw-away hotmail account for that :-)
Jan 16
parent Andrea Fontana <nospam example.org> writes:
On Tuesday, 16 January 2024 at 13:54:33 UTC, Siarhei Siamashka 
wrote:
 An argument against this is that in the long run github may 
 eventually deteriorate or go belly up. And this is a risk. 
 Similar to what happened to the sourceforge.net platform. The 
 git source repository can be easily mirrored anywhere else. But 
 the issue tracker is a pain to migrate.
You can export issues with a cronjob.
Jan 16
prev sibling next sibling parent Dennis <dkorpel gmail.com> writes:
On Tuesday, 16 January 2024 at 13:27:14 UTC, Andrea Fontana wrote:
 I still don't get why we're not using github for issues in 2024.
Robert has finished the migration tool, and AFAIK just needs to finish the changelog generator now: https://github.com/dlang/tools/pull/466
Jan 16
prev sibling parent reply Jonathan M Davis <newsgroup.d jmdavisprog.com> writes:
On Tuesday, January 16, 2024 6:27:14 AM MST Andrea Fontana via Digitalmars-d 
wrote:
 On Tuesday, 16 January 2024 at 00:32:13 UTC, user1234 wrote:
 With all what's going on, I wanted to remind you that. In case
 you want it to be ever fixed. Roger this ?

 https://issues.dlang.org/
I still don't get why we're not using github for issues in 2024.
Personally, I don't get why you'd use github issues when you have bugzilla, because bugzilla is a superior tool for dealing with bug reports. Github issues make a lot of sense for small projects where you don't want to go to the trouble of setting up your own instance of bugzilla, but for larger projects, they're a mess in comparison. That being said, D management has been convinced to switch to using github issues, and work is being done on migrating the issues on bugzilla to github, but it takes time. I think that they're getting close to pulling the trigger on it though. - Jonathan M Davis
Jan 16
parent reply Hipreme <msnmancini hotmail.com> writes:
On Tuesday, 16 January 2024 at 17:04:09 UTC, Jonathan M Davis 
wrote:
 On Tuesday, January 16, 2024 6:27:14 AM MST Andrea Fontana via 
 Digitalmars-d wrote:
 On Tuesday, 16 January 2024 at 00:32:13 UTC, user1234 wrote:
 With all what's going on, I wanted to remind you that. In 
 case you want it to be ever fixed. Roger this ?

 https://issues.dlang.org/
I still don't get why we're not using github for issues in 2024.
Personally, I don't get why you'd use github issues when you have bugzilla, because bugzilla is a superior tool for dealing with bug reports. Github issues make a lot of sense for small projects where you don't want to go to the trouble of setting up your own instance of bugzilla, but for larger projects, they're a mess in comparison. That being said, D management has been convinced to switch to using github issues, and work is being done on migrating the issues on bugzilla to github, but it takes time. I think that they're getting close to pulling the trigger on it though. - Jonathan M Davis
1. Because everyone is on GitHub 2. Bugzilla is a much older tool with an unfriendly interface even though plenty of people got used to it. 3. Bugzilla currently does not accepts gmail accounts to be created, with it is a big shoot in the foot 4. I personally find bugzilla a lot inferior on navigation and user discussion
Jan 16
parent jmh530 <john.michael.hall gmail.com> writes:
On Tuesday, 16 January 2024 at 17:26:11 UTC, Hipreme wrote:
 On Tuesday, 16 January 2024 at 17:04:09 UTC, Jonathan M Davis 
 wrote:
 On Tuesday, January 16, 2024 6:27:14 AM MST Andrea Fontana via 
 Digitalmars-d wrote:
 On Tuesday, 16 January 2024 at 00:32:13 UTC, user1234 wrote:
 With all what's going on, I wanted to remind you that. In 
 case you want it to be ever fixed. Roger this ?

 https://issues.dlang.org/
I still don't get why we're not using github for issues in 2024.
Personally, I don't get why you'd use github issues when you have bugzilla, because bugzilla is a superior tool for dealing with bug reports. Github issues make a lot of sense for small projects where you don't want to go to the trouble of setting up your own instance of bugzilla, but for larger projects, they're a mess in comparison. That being said, D management has been convinced to switch to using github issues, and work is being done on migrating the issues on bugzilla to github, but it takes time. I think that they're getting close to pulling the trigger on it though. - Jonathan M Davis
1. Because everyone is on GitHub 2. Bugzilla is a much older tool with an unfriendly interface even though plenty of people got used to it. 3. Bugzilla currently does not accepts gmail accounts to be created, with it is a big shoot in the foot 4. I personally find bugzilla a lot inferior on navigation and user discussion
5. Positives and negatives of both approaches were known at the time and the decision was made under the condition that the user experience would be basically the same (e.g. not only issues would get migrated, but also comments, which caused some issues for a time I believe). Changing now would just be a big waste of people's time*. * I know that's a sunk cost fallacy, but it falls well within the recent discussion of social-technical issues in managing the D language.
Jan 16