kevin added a new comment to an issue you are following:
``
The last few times we have branched off the new release, then switched rawhide compose to
use the new rawhide key and made sure everything was signed with that key.
So we could:
* Just sign one package with the new key at branch point: fedora-release. This would allow
them to update fedora-repos and import the new key.
* Wait some time (a day? a week?)
* switch everything over to the new key.
Or I suppose we could just set a dedicated rawhide key and never change it. I really
don't like that because if we do have to change it, we have no good way to. ;(
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7445