Bugzilla to GitHub Issues Migration
Vladimir Panteleev
thecybershadow.lists at gmail.com
Sat Jun 24 07:08:36 UTC 2023
On Saturday, 24 June 2023 at 01:55:11 UTC, Mike Parker wrote:
> If you know of anything else, please let us know.
Contributor documentation (CONTRIBUTING.md, maybe the wiki?).
>> 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.
Here are the first two:
https://github.com/dlang/dlang-bot/pull/302
https://github.com/dlang/tools/pull/461
More information about the Digitalmars-d
mailing list