Bugzilla to GitHub Issues Migration (page 2)

On Thursday, 22 June 2023 at 08:33:24 UTC, Adam Wilson wrote: > On Thursday, 22 June 2023 at 02:40:01 UTC, Mike Parker wrote: >> >> There's a JSON file that matches Bugzilla IDs with GH IDs. Yours are in there. I don't know if there's a way via the GH API to automatically subscribe users to specific issues, or if the app does it. If there is and it doesn't, then that seems like something we should consider adding. >> >> Again, I'll defer to Robert for the details. > > Will this work with email address's that are not the primary in GH? My Bugzilla email is different than my GH, so I added my Bugzilla email as a secondary email in GH. Not sure what the "this" in your question refers to.

June 22, 2023

Re: Bugzilla to GitHub Issues Migration

Posted by Vladimir Panteleev
in reply to Mike Parker

Permalink

Vladimir Panteleev

Posted in reply to Mike Parker

Permalink

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?

On Thursday, 22 June 2023 at 07:03:00 UTC, Mike Parker wrote: > All of that's going to require coordinating with Brad, so I can't really put it on a timeline. I have been waiting for over a year now to get the missing files from Brad for the new Bugzilla, so we probably probably shouldn't hold our breath on this.

On 6/21/2023 9:46 AM, Mike Parker wrote: > If you're aware of anything out there that we need to consider once the issues are migrated, please let us know here. Need an algorithm where links to bugzilla will be converted to the correct github issue link.

On 6/21/2023 7:34 PM, Mike Parker wrote: > It appears nothing is done with the keywords, and I don't recall any discussion about it. Do you think they should become labels, or perhaps added as a list in the text of the GH issue? Do we *need* to keep them on the GH issue? I rely on them a lot. When I enter bug fixing mode for a particular topic, such as DLLs, I rely on the DLL keyword to give me an overview of all the issues with DLLs. It takes a bit to get up to speed on a particular topic, so it's more efficient to deal with several closely related issues at a time. So, yes, I need them, and converting them to labels sounds ideal.

On Thursday, 22 June 2023 at 18:56:19 UTC, Walter Bright wrote:

On 6/21/2023 9:46 AM, Mike Parker wrote:

If you're aware of anything out there that we need to consider once the issues are migrated, please let us know here.

Need an algorithm where links to bugzilla will be converted to the correct github issue link.

I think this is doable in the following way:

Create a new GitHub repository, e.g. github.com/dlang/issues
Transfer the issues from Bugzilla, taking care to preserve the issue number. So, https://issues.dlang.org/show_bug.cgi?id=12345 is recreated at https://github.com/dlang/issues/issues/12345
Move the issue from the issues project to the corresponding project (e.g. dmd).

Moving the issue will leave behind a redirect, so that https://github.com/dlang/issues/issues/12345 will continue to work and therefore allow a trivial remapping. This will be useful should we eventually decide to completely retire Bugzilla and replace it with a site that only hosts redirects.

Forums