Bugzilla to GitHub Issues Migration (page 6)

On Friday, 23 June 2023 at 16:02:53 UTC, Mike Parker wrote:

So we've put the brakes on things for now. Robert is going to reach out to GitHub to see if they can do something for us like they did for LLVM. Then we'll hopefully be able to push the issues to GitHub under the original poster's handle. Of the issues raised here, that's the one thing we can't manage on our own.

Hey, we also need to make sure our infra is ready for this. The bots and the changelog generator need to be updated, at least.

I think the following plan will work:

Update DBot to only accept "Fix Bugzilla" instead of "Fix Issue". Put up a warning if the old string is used.
Update the changelog generator to accept both.
When the next release is cut, open up GitHub issues for our projects. (This is orthogonal to migrating issues from Bugzilla, right?) Users can now start filing bugs on GitHub.
Change DBot to accept both "Fix Bugzilla" and "Fix #xxxxx" where the latter refers to a GitHub issue. GitHub can auto-close referenced issues itself, so we may not need DBot to do anything here.
Migrate the issues one by one, leaving behind links on Bugzilla.
Make Bugzilla read-only.

I could work on DBot and the changelog generator?

On 6/23/2023 6:01 AM, Mike Parker wrote: > For the record, I intend to create a special account for adding the issues to GitHub (e.g., "bugzilla_migration"). I certainly don't want them all in my name. I don't see how we can post them as the original user, though. From what I understand, it requires the id and a token. Can we add the original contributor as a comment?

On Friday, 23 June 2023 at 18:29:53 UTC, Walter Bright wrote: > On 6/23/2023 6:01 AM, Mike Parker wrote: >> For the record, I intend to create a special account for adding the issues to GitHub (e.g., "bugzilla_migration"). I certainly don't want them all in my name. I don't see how we can post them as the original user, though. From what I understand, it requires the id and a token. > > Can we add the original contributor as a comment? That already happens. The comment has a header with the contributor's name and the date it was submitted. E.g., https://github.com/dlang/bz2gh-test/issues/109 In the actual migration, the GitHub contributor and everyone on the CC list will get `@` tagged in the comment. However, it will be much better if we can submit the issue in the contributor's name.

June 24, 2023

Re: Bugzilla to GitHub Issues Migration

Posted by Mike Parker
in reply to Vladimir Panteleev

Permalink

Mike Parker

Posted in reply to Vladimir Panteleev

Permalink

On Friday, 23 June 2023 at 17:56:44 UTC, Vladimir Panteleev wrote:

On Friday, 23 June 2023 at 16:02:53 UTC, Mike Parker wrote:

Hey, we also need to make sure our infra is ready for this. The bots and the changelog generator need to be updated, at least.

Yes, we've discussed the bot, but the changelog generator hasn't come up. We need to be aware of anything in the ecosystem that may be affected. If you know of anything else, please let us know.

I think the following plan will work:

Update DBot to only accept "Fix Bugzilla" instead of "Fix Issue". Put up a warning if the old string is used.
Update the changelog generator to accept both.
When the next release is cut, open up GitHub issues for our projects. (This is orthogonal to migrating issues from Bugzilla, right?) Users can now start filing bugs on GitHub.
Change DBot to accept both "Fix Bugzilla" and "Fix #xxxxx" where the latter refers to a GitHub issue. GitHub can auto-close referenced issues itself, so we may not need DBot to do anything here.
Migrate the issues one by one, leaving behind links on Bugzilla.
Make Bugzilla read-only.

That looks like a good approach.

I could work on DBot and the changelog generator?

I would love that. I'll pull you into our next discussion about it.

On Saturday, 24 June 2023 at 07:08:36 UTC, Vladimir Panteleev wrote: > ... > Here are the first two: > ... Awesomeand I think It would be cool if this proccess was recorded to be used later as how this migration problem was fuxed as a showcase for the D community. Matheus

Forums