Bugzilla to GitHub Issues Migration

Timon Gehr timon.gehr at gmx.ch
Fri Jun 23 15:52:16 UTC 2023


On 6/23/23 15:01, Mike Parker wrote:
> On Friday, 23 June 2023 at 12:31:39 UTC, Timon Gehr wrote:
>> On 6/23/23 11:53, Robert Schadek wrote:
>>>>
> 
>>
>> Yes, unfortunately it is true that many people won't report issues on 
>> bugzilla. Preserving the existing issues is still really important as 
>> well. Those are issues reported by _enthusiastic people who let 
>> themselves be assed to report on bugzilla_, and we owe them to treat 
>> their issues well. In particular, I think moving issues to github 
>> issues and giving all the github contributions/authorship for those 
>> issues to yourself and Mike is a terrible way to move forward, even if 
>> the issues are technically in the public domain and/or belong to DLF.
> 
> 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.

My preference order:
1. Migrate all information that has a correspondence on github perfectly
2. Keep bugzilla, additionally allow github issues for new reports, 
synch issues into bugzilla
3. Keep status quo
4. Migrate single comments as bugzilla_migration user
5. ...

Of course, that's just my preference, not all of those are the same 
amount of effort, and some effort has already been spent. It would be 
great to explore Vladimir's suggestions. If we can do what LLVM did, 
that would be awesome.


More information about the Digitalmars-d mailing list