Good Morning Everyone, Tomorrow we are planning on deploying a new version of pagure and pagure-dist-git on production. These changes come with two changes to the packager workflow: * Anitya integration in dist-git Something we lost when loosing pkgdb was the easy integration to anitya (https://release-monitoring.org). With the coming changes we are getting them back. On the left hand-side column, there will be a drop-down button allowing to change the settings for anitya for the project. Existing status will be migrated from the fedora-scm-requests repo on pagure to use this drop-down. Using the fedora-scm-requests repo for the anitya integration will no longer be supported. * Change in the de-orphaning process Currently if a package is orphaned, one has to open a ticket against the releng project to adopt it. With these changes, anyone will be able to adopt orphaned projects (not retired on master) directly from dist-git's UI. If the project is retired or has been orphaned for too long, a ticket on the releng project will still be required though. Both of these changes can already be reviewed in staging at: https://src.stg.fedoraproject.org Looking forward for your feedback! Pierre _______________________________________________ devel-announce mailing list -- devel-announce@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-announce-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
