Bugzilla to GitHub Continued

[Nick Treleaven]

On Tuesday, 4 July 2023 at 10:34:44 UTC, Mike Parker wrote:
> * the author of each issue and everyone on the CC list will 
> have their GitHub handles `@` tagged in the initial comment
> * each comment on the Bugzilla issue will be posted separately 
> on the GitHub issue

Great work!

> * text from Bugzilla will be posted to GitHub in Markdown code 
> blocks to avoid formatting issues

That might mean a long paragraph would appear as a really long 
line that has to be horizontally scrolled to read it.

> * GitHub labels will be created from Bugzilla keywords and 
> applied to the new GitHub issues as appropriate

Great!

> * the original Bugzilla issue will be updated with a link to 
> the new GitHub issue and a note that further comments on the 
> Bugzilla issue may not be seen

OK, so we continue using bugzilla for each issue until we see 
that comment? With the rate limit gone, I'm guessing it shouldn't 
take too long.

> I think that addresses most of the concerns raised about the 
> format of the issues in the previous discussion. Are we missing 
> anything?

Will the issues forum get github updates for new issues, status 
updates and comments?

> At some point after the migration, we'll put the Bugzilla 
> instance into read-only mode. We've never intended to shut it 
> down. We need to migrate it to a server under our control 
> eventually. Once it's set to read-only, we'll want dlang-bot to 
> still be able to have write access so that it can close issues 
> on Bugzilla when the associated issues on GitHub are closed.

So will dlang-bot close a matching github issue as well as the 
bugzilla one? Can PRs made after the migration just use e.g. 
`Fixes #123` and dlang-bot will be able to find any corresponding 
bugzilla issue?

Thanks to everyone working on this. Looking forward to formatting 
in issue comments, better mobile UX (no more tiny text), better 
issue searching, better integration with github projects, issue 
link tooltips etc.