On 12/1/25 9:27 AM, Jakub Kadlcik via copr-devel wrote:
Everything is explained in this blog post:
https://fedora-copr.github.io/posts/migrating-copr-results-to-pulp
Please let us know if you have any questions or concerns,
From the blog post:
> While your projects are being migrated, all your builds and actions
> will be stuck in the “pending” state until the migration is finished.
... and ...
> For technical reasons, we won’t notify users directly that their
> projects are about to be migrated. Please see the Pulp Migration
> Schedule to get a rough estimate of when you could be affected.
That's certainly not ideal.
My question, though, is whether there will be any user-visible
indication during a migration that this is the reason that everything is
stuck. Otherwise, I can foresee a flood of tickets, emails, etc. when
(months from now) things appear broken.
--
========================================================================
If your user interface is intuitive in retrospect ... it isn't intuitive
========================================================================
--
_______________________________________________
copr-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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.fedorahosted.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
