Bugzilla to GitHub Issues Migration

[Vladimir Panteleev]

On Thursday, 22 June 2023 at 02:34:46 UTC, Mike Parker wrote:
> On Wednesday, 21 June 2023 at 16:51:13 UTC, Johan wrote:
>
>>
>> Do you have a link to a document that describes what the 
>> migration will do? (e.g. what will be done with the keywords, 
>> numbering, people on CC list, etc.)
>>
>
> No, there's no document. I've made the test repository public 
> so you can see what the issues look like on GH:
>
> https://github.com/dlang/bz2gh-test/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc

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.

- 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.

- 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.

- 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?