A recurring issue at branching/beta/release time is that the appstream metadata for the Fedora Linux distribution itself, used by Discover to figure out if it should offer an update, is not updated / synced in time.
One the reason that this is implemented this way is that this is how this works right now in Discover.
The second reason is that the release schedule has been very inconsistently maintained over the last few years, making it difficult to rely on it for the metadata: https://pagure.io/fedora-pgm/schedule/issue/118
Ideally, we would keep shipping the released versions in an appstream metadata file in an RPM package but we would complement that with metadata fetched from the Fedora infra.
We should probably be using https://github.com/ximion/appstream/pull/436 (and making sure that this behaves properly on slow networks and offline).
See the discussion in: https://bugzilla.redhat.com/show_bug.cgi?id=2311964
To give an idea of the work that would be avoided, here is the collection of updates that we need to do as F41 has been pushed back by one week: bz, f41, f40, f39
Metadata Update from @siosm: - Issue set to the milestone: Fedora Linux 42
Log in to comment on this ticket.