Bugzilla to GitHub Issues Migration

[Vladimir Panteleev]

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:

1. Update DBot to only accept "Fix Bugzilla" instead of "Fix 
Issue". Put up a warning if the old string is used.
2. Update the changelog generator to accept both.
3. 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.
4. 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.
5. Migrate the issues one by one, leaving behind links on 
Bugzilla.
6. Make Bugzilla read-only.

I could work on DBot and the changelog generator?