Migration to GitHub Issues

[radioactiveman]

As mentioned in our previous announcement, we intend to transition away from Redmine to GitHub.

After enabling (GitHub) discussions here the next step will affect our bug tracker. The plan is to migrate all previous bug reports with the tool redmine2github. I have already tested it successfully in a smaller scale and want to start with the actual migration in April.

Important thing to know is that GitHub will send notifications for every issue and comment to all persons who watch our GitHub repo.
To avoid receiving hundreds of emails please adjust your notification settings for the main audacious project.

Either configure custom settings like in the screenshot below and uncheck issues or simply disable notifications temporarily.
I will keep you updated about the current migration status here.

[radioactiveman]

Current status:

• Create a separate GitHub user for the migration
• Enable GitHub issues
• Run the actual migration
• Copy attachments of open issues
• Clean-up the issue labels and milestones
• Add templates for issues / feature requests
• Update the bug tracker links on our website and in Git
• Retire Redmine and make it read-only

[radioactiveman]

Unfortunately an unexpected issue occurred:

My plan was to migrate all Redmine issues to GitHub so they have the same issue number to keep references from commits or changelogs working. However GitHub uses the same counter for Issues, Pull Requests and Discussions. Our "first" issue here on GitHub starts now with number 135...

@jlindgren90: How should we proceed now? Does it make sense to you to still migrate all issues from Redmine? Or should we just focus on the open ones?

[jlindgren90]

I'd vote for migrating all of them as planned. Then we have a backup (of sorts) of the Redmine data even if the numbers don't match up.

[jlindgren90]

I don't like that, then we lose all the pull request history.