Dear users, developers and maintainers of PKI,
We, the Dogtag PKI team, have decided to use GitHub issues as our primary issue tracker. As a part of the effort to keep things unified, we will be migrating all the issues (open and closed) from Pagure Issues to GitHub Issues.
We see several advantages by this migration:
Reported issues and code stay closer
Better ways to refer/track issues within PRs and commits
Better audience outreach
When?
Migration starts on Friday, Oct 2 (~5PM EST) and we anticipate it to end by Oct 4.
Dry Run Results
https://github.com/pki-bot/pki-issues-final/issues
Process:
We are planning to do the migration in 4 stages.
Stage 1 (~5 hours):
Copy all issues from Pagure to GitHub. We have identified and tried to map the users from Pagure to GitHub. If your nickname is listed in [1], you’ll be receiving github notifications and/or emails. Unfortunately, there is no way to keep it down.
Stage 2 (~2 hours):
This is a check stage where we test if every Pagure issue has been copied to GitHub correctly. There will be no notifications generated
Stage 3 (~2 hours):
Add comments to ALL pagure issues and close ALL OPEN pagure issues as Migrated. The comment will include a link to the corresponding GH issue. We have placed a request [2] to turn off notifications during this stage.
Stage 4 (~1 hours):
Update associated bugzilla with link to new GitHub Issues. The “Devel Whiteboard” will be updated in the format `PKI <GH issue number>` and an external tracker to the GH issue will be added. There will be no notifications generated in this stage.
Migration Tool:
The tool is available in GH: https://github.com/SilleBille/pagure2github/
Problems?
In case you find any bugs or problems in the migrated tickets, feel free to reach out to us via pki-users@redhat.com
Dogtag PKI Team
[1] https://github.com/SilleBille/pagure2github/blob/master/lib/pagure2github/__init__.py#L43-L123