Describe the issue

Right now the process at https://docs.fedoraproject.org/en-US/websites/fedora-release/ is, in significant part, "collect release-specific information from the people who know it and write it in some yaml files".

"Release specific information" is things like RC # is "gold", which architectures and spins are part of the release, which GPG key was used, what the release checksums are, and so on. Rather than having this manual communication process, or leaving the websites team to effectively guess, it makes sense to me to just have release-engineering write that information to the metadata file as part of the general release process

When do you need this? (YYYY/MM/DD)

Ideally, in place for F32 beta (so before 2020-03-17).

When is this no longer needed or useful? (YYYY/MM/DD)

Always useful

If we cannot complete your request, what is the impact?

As the process is imagined now, people not familiar with what's needed are likely to be newly involved every time, and their scrambling to find what's needed and ask the right questions is actually a lot more work (all around!) than just having the people who are directly familiar with the relevant information put it in a standard machine-readable location as part of the process.