Bugzilla to GitHub Issues Migration

[Mike Parker]

On Thursday, 22 June 2023 at 15:50:06 UTC, Vladimir Panteleev 
wrote:

>
> I still see some issues:
>
> - Please import one BZ comment as one GH comment, so that it's 
> still possible to link to a comment. Comments to links should 
> be converted to point to the right comment, or else we may lose 
> context.
>
> - Please put the description and every comment in a Markdown 
> block, otherwise things are going to be corrupted due to the 
> Markdown formatting.

Sounds good. I'll discuss it with Robert.

>
> - Please try it with some bugs from the DMD project before 
> doing the real migration. You should see a much higher variety 
> of "interesting" bug reports that you would not see otherwise.
>
> - Make sure to actually try moving ALL bugs to a private test 
> repository before doing the real migration, for the same 
> reasons.

Agreed.


>
> - Have you considered using the same software that the LLVM 
> project used for their migration? Writing our own tool seems 
> wasteful if existing proven software exists.

I didn't look into it. I think Mathias did when he first explored 
this a couple years ago, but I may be wrong.

>
> - We have agreed that a prerequisite of doing this migration 
> was ensuring that we can still download the entire data off of 
> GitHub, and/or that we maintain a live independent copy/backup 
> in case we lose access to the data. Has this been done?

There are a few different options out there for this. We can 
download everything anytime via GitHub's API. GH actually 
[released a tool for 
this](https://github.com/github/github-artifact-exporter) a 
couple of years ago, but archived the repo a few months back. 
However, I'm leaning toward a paid service that makes regular 
backups of designated repositories to a cloud storage provider 
(which would be Google Drive in our case).