Good Morning Everyone, The Fedora Infrastructure team has been working on making changes to the way orphaned packages are being adopted as well as the way to set the monitoring status for the integration with anitya (ie: https://release-monitoring.org). ## Orphan packages Currently if a package is orphaned there is no way to adopt it easily on dist-git (https://src.fedoraproject.org). You need to open a ticket on the releng issue tracker and wait for someone to process that ticket. This is going to change, new versions of pagure-dist-git and pagure will offer a button on the left hand side menu offering to adopt orphaned packages. This is already live in staging, so you can see how it looks there, for example: https://src.stg.fedoraproject.org/rpms/aasaver (you'll need to be logged in) Note: if the package is retired, you will still have to go through a releng ticket as it will need to be unblocked in koji. ## Anitya integration Currently if you want to tweak the setting for the anitya integration, you need to open a pull-request on the fedora-scm-requests project at https://pagure.io/releng/fedora-scm-requests/ That git repo is pretty big and once your pull-request is finally open, you still have to wait for someone to merge it. This is also going to change, new versions of pagure and pagure-dist-git offer a drop-down menu on the left hand side menu to see and adjust the monitoring status of the project. This is also live in staging and you can see an example of a project who has set its monitoring status to "monitoring": https://src.stg.fedoraproject.org/rpms/0ad (The status in staging have been imported from the fedora-scm-requests repo) ## Feedback Feel free to play with this in staging and let us know if there is anything that isn't working as expected or that you would like to change before we push this to production (post F31-beta freeze). Once the new versions of pagure, pagure-dist-git, anitya and the-new-hotness have been deployed to production we will send another announcement for the change and work on getting the different documentations updated. Looking forward to hear from you, Michal and Pierre - On behalf of the Fedora Infrastructure team _______________________________________________ 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
