Bugzilla to GitHub Issues Migration

[Mike Parker]

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

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

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.