[Pki-devel] Dogtag PKI is migrating issue tracker from Pagure to GitHub

[Dinesh Prasanth Moluguwan Krishnamoorthy]

Dear users, developers, and maintainers of PKI,


We are happy to announce that the migration of issues from Pagure to Github
was a success.

You can now browse the issues filed against Dogtag PKI on Github:
https://github.com/dogtagpki/pki/issues/


The Pagure Issue tracker is now set to "read-only", to prevent any
comments/modifications that may no longer

be monitored. A link to the associated Github issue has been added as a
comment to the associate Pagure issue

to make it easy for users to track their issues.


All attachments (patches, logs, etc) have been ported to GitHub as well.
So, *none of the information should be*

*lost by this migration.*


All associated Bugzilla bugs have been updated to track the corresponding
new GitHub issues.


If you find any issues, feel free to write back to us and we will try to
fix it! Thanks for your understanding and we apologize

for any inconvenience caused by this migration.


Dogtag PKI Team




On Thu, Oct 1, 2020 at 5:58 PM Dinesh Prasanth Moluguwan Krishnamoorthy <
dmoluguw at redhat.com> wrote:

> 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
> <https://pagure.io/dogtagpki/issues> to GitHub Issues
> <https://github.com/dogtagpki/pki/issues>.
>
> We see several advantages by this migration:
>
>    1.
>
>    Reported issues and code stay closer
>    2.
>
>    Better ways to refer/track issues within PRs and commits
>    3.
>
>    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 at redhat.com
>
> Dogtag PKI Team
>
> [1]
> https://github.com/SilleBille/pagure2github/blob/master/lib/pagure2github/__init__.py#L43-L123
>
>
> [2] https://pagure.io/fedora-infrastructure/issue/9361
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pki-devel/attachments/20201005/491f7400/attachment.htm>