Change Log Generator Fix?

[jmh530]

I noticed on a separate thread [1] an issue with the nightly 
change log related to an importC fix.

It looks like issues with the change log generator are related to 
the Bugzilla-> Github transition. In one thread Dennis suggested 
[2] that the issue would fix itself after release 2.111.0 (the 
latest release as of this writing). Maybe the issue is persisting 
with the nightly but will be fixed once 2.112.0 is released? I 
also found a meeting summary from March [3] that suggested a 
one-line macro was needed to fix it (but again that was March).

Regardless, I hope this gets resolved sooner rather than later. I 
don't think it's very professional to to have incorrect change 
logs.

Along the same lines, I think it also would make sense to assign 
someone the task of going through the affected change logs and 
fix them, either manually or automatically when the generator 
works properly again (if it doesn't already).

[1] 
https://forum.dlang.org/post/toiqvqkisjnumfiqxgzv@forum.dlang.org

[2] 
https://forum.dlang.org/post/bgdzjkknrgnkteohaqah@forum.dlang.org

[3] 
https://forum.dlang.org/post/zbzfmwphlmmlfqhbadxt@forum.dlang.org