https://pagure.io/releng/issue/12001

We'd like to have *Fedora Rawhide +1* gpg keys generated about ~2 (or maybe 4 weeks, if that's not a big issue) *before the branching event* happens. Right now it seems to be done [on T-1 day](https://docs.fedoraproject.org/en-US/infra/release_guide/mass_branching_checklist/) which is most of the time OK, but sometimes quite stressful.

The first part of the request is perhaps about making a policy/rule, best-effort TODO item, or something like that. Dunno, ideas? So we could expect that Rawhide+1 keys keep appearing soon enough.

As an additional wish (sub-request), it would be nice to let people know that this key-generating event happened. The background story is that that this triggers events/processes in external teams (Mock, distribution-gpg-keys, Fedora Copr, Fedora CI, Packit, ...). I'm listening for the `fedora-repos` changes myself, and I'll try to start our external workflows "manually".. But I'm just an individual (and I make mistakes) ... so a question comes to my mind; can the `update distribution-gpg-keys package` become part of the branching process perhaps? (sure, we would process such task)

• When do you need this?
  Before the next f42 branching. Then we can implement a trivial fix for [the related mock-core-configs issue](https://github.com/rpm-software-management/mock/issues/1338)

• If we cannot complete your request, what is the impact?
  If nothing happens, then we'll do what we are used to "externally"; and we'll keep trying to make the release `mock-core-configs` package "in time", and it will often work. But having keys sooner, we would have much less timing pressure and the 1338 issue(https://github.com/rpm-software-management/mock/issues/1338) wouldn't repeat for sure.