need to have the final release configuration set in fedora-release and
Marking as an accepted blocker under the Release identification criteria as
don't forget generic-release and generic-repos too, while we're at it. and we'll need a spin-kickstarts build when that settles down, i'll file another bug for that.
there is no generic-repos but we will look at generic-release
It would be worthwhile to look at the metadata expiration on the base fedora repo. I think it's currently commented out, thus the default is quite low (48 hours in dnf, I believe). Is there a reason for this short expiry on a repo that doesn't change after release?
metadata expiration in fedora repo is 7days which is supposed to tell dnf to not look for a week and it is only supposed to fetch if something changes. if dnf is not doing the right thing it is a dnf bug. there is some issues with the transition from pre release to GA where users would not see updates as they have stale fedora metadata
generic-release-25-1 fedora-release-25-1 fedora-repos-25-1 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-7b70ad9b8e
fedora-release-25-1, fedora-repos-25-1, generic-release-25-1 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-7b70ad9b8e
fedora-release-25-1, fedora-repos-25-1, generic-release-25-1 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.