On Wed, Jun 21, 2023 at 04:46:06PM +0000, Mike Parker via Digitalmars-d wrote:
> We're much closer now to pulling the trigger on the Bugzilla to GitHub issues migration. Robert has fixed the blocker in the app he wrote to perform it, and he and I have both confirmed that it works as expected on a test repository.
> 
> We have a planning session scheduled this week. Before I initiate the migration, I need to make sure we're aware of all of the consequences and how to handle them (e.g., dlang-bot, moving Bugzilla to read-only, any instructions on the Wiki, etc.).
> 
> If you're aware of anything out there that we need to consider once the issues are migrated, please let us know here.
[...]

How will existing accounts on Bugzilla be handled?  I have a list of issues I'm monitoring on Bugzilla, but I don't think there will be an easy way to import these to Github.  It will not be automatic, for sure, since I use different credentials for both.  But it will be painful to have to manually resubscribe to individual issues on my monitor list. Is there any way to semi-automate this?


T

-- 
Маленькие детки - маленькие бедки.

On Wednesday, 21 June 2023 at 17:01:31 UTC, H. S. Teoh wrote:

>
> How will existing accounts on Bugzilla be handled?  I have a list of issues I'm monitoring on Bugzilla, but I don't think there will be an easy way to import these to Github.  It will not be automatic, for sure, since I use different credentials for both.  But it will be painful to have to manually resubscribe to individual issues on my monitor list. Is there any way to semi-automate this?
>
>

There's a JSON file that matches Bugzilla IDs with GH IDs. Yours are in there. I don't know if there's a way via the GH API to automatically subscribe users to specific issues, or if the app does it. If there is and it doesn't, then that seems like something we should consider adding.

Again, I'll defer to Robert for the details.

On Thu, Jun 22, 2023 at 03:17:35AM +0000, Andrej Mitrovic via Digitalmars-d wrote: [...]
> One thing that will be hard to keep track of is finding the list of active bugs that a person has filed since the issue author on Github will be different.
> 
> But maybe that's not a problem if we let Bugzilla stay up in read-only mode?
> 
> Otherwise if Bugzilla will be shut down I'd suggest adding something like `reported-by: <user>` in the transferred issue's comment to perhaps make it easy to search using the Github UI?
> 
> This shouldn't block migration, a comment like this can easily be added later on.
> 
> The use-case here is I like to keep track of bugs I've opened to see if any have been resolved. When they get resolved I can remove any relevant workarounds in my code.

Me too!

Perhaps Bugzilla get stay up temporarily during the transition period, read-only to users but perhaps writeable to say the dlang bot, so that when github issues get closed Bugzilla can be updated too? It would be annoying to track otherwise.  I have several projects with version()'d workarounds named like `version(bug12345)`; when the bugzilla issue is closed I can search for these and disable them.  But after the GH migration issue numbers will change, and this makes it hard to track what's fixed.


T

-- 
Trying to define yourself is like trying to bite your own teeth. -- Alan Watts

On Thursday, 22 June 2023 at 04:31:42 UTC, H. S. Teoh wrote:
> On Thu, Jun 22, 2023 at 03:17:35AM +0000, Andrej Mitrovic via Digitalmars-d wrote: [...]
>> One thing that will be hard to keep track of is finding the list of active bugs that a person has filed since the issue author on Github will be different.
>> 
>> But maybe that's not a problem if we let Bugzilla stay up in read-only mode?
>> 
>> Otherwise if Bugzilla will be shut down I'd suggest adding something like `reported-by: <user>` in the transferred issue's comment to perhaps make it easy to search using the Github UI?
>> 
>> This shouldn't block migration, a comment like this can easily be added later on.
>> 
>> The use-case here is I like to keep track of bugs I've opened to see if any have been resolved. When they get resolved I can remove any relevant workarounds in my code.
>
> Me too!
>
> Perhaps Bugzilla get stay up temporarily during the transition period, read-only to users but perhaps writeable to say the dlang bot, so that when github issues get closed Bugzilla can be updated too? It would be annoying to track otherwise.  I have several projects with version()'d workarounds named like `version(bug12345)`; when the bugzilla issue is closed I can search for these and disable them.  But after the GH migration issue numbers will change, and this makes it hard to track what's fixed.
>
>

The Bugzilla instance isn't going anywhere. At some point, we need to get it migrated away from Brad's server to a DLF server so that we can have full admin access and ensure that it stays around. I like the idea of keeping dlang-bot's write access once it goes read-only. All of that's going to require coordinating with Brad, so I can't really put it on a timeline.

On Thursday, 22 June 2023 at 02:40:01 UTC, Mike Parker wrote:
> On Wednesday, 21 June 2023 at 17:01:31 UTC, H. S. Teoh wrote:
>
>>
>> How will existing accounts on Bugzilla be handled?  I have a list of issues I'm monitoring on Bugzilla, but I don't think there will be an easy way to import these to Github.  It will not be automatic, for sure, since I use different credentials for both.  But it will be painful to have to manually resubscribe to individual issues on my monitor list. Is there any way to semi-automate this?
>>
>>
>
> There's a JSON file that matches Bugzilla IDs with GH IDs. Yours are in there. I don't know if there's a way via the GH API to automatically subscribe users to specific issues, or if the app does it. If there is and it doesn't, then that seems like something we should consider adding.
>
> Again, I'll defer to Robert for the details.

Will this work with email address's that are not the primary in GH? My Bugzilla email is different than my GH, so I added my Bugzilla email as a secondary email in GH.