We have not done this in the past. Pushing out betas and such is a large effort on the part of release engineering and mirrors who usually need 2-3 days notice before they go live. RC's get updated regularly and do not have that gap in time to allow mirrors to catch up. So usually RC's are meant for people who are doing specific testing against known blockers and regressions versus general downloads.

Yeah, this is by design. We actually release a beta (which has some number of RC's until it passes) and final (likewise).

We don't want to advertise an "RC" as a final release, or even a beta. There's often issues in RC's that might be new from the last released milestone.
Also, RC's sometimes come really fast. It would be a lot of changes to try and advertise them each time (sometimes multiple ones per day).

It may be that we want to stop advertising the beta after a while, or perhaps point people to the QE pages so they can properly test.

Note there's some versioning confusion here. The images linked on getfedora are Beta-1.3. That is the official Beta release: we signed off on the Beta-1.3 compose. The thing available on getfedora is not RC-1.3, that's a different thing.

The process here is we do Beta candidates (which are labelled Beta-1.1, Beta-1.2, Beta-1.3 and so n), sign one off, and that's the Beta, which is offered as such until Final is done. Then we build Final candidates (which are labelled RC-1.1, RC-1.2, RC-1.3 and so on) , sign one off, and the one that's signed off becomes the Final release and is offered as such.

We never publicize the candidate composes on getfedora or anywhere else "public facing".

Thank you everyone for the insightful explanations.