Got *90 too…I suppose that there is a secret flag that prevents “pre” updates to be installed, just a guess. Does any one know how and when exactly a release that is visible online is actually visible for swupd?
We have some ideas for making that happen - we’ll keep you posted.
Also remember that just because a build is made, doesn’t mean that it gets released. We do have an extensive suite of QA tests that get run, and it’s always possible that there may be a showstopper bug that blocks release of a build. In this case though 31110 is now live.
Cool! I am looking forward to reading some news about this.
@pixelgeek Could you please explain, why my swupd cannot see the "pre"release whereas in the repo the "pre"release is visible. What function decides when a release can be downloaded? Is it my local swupd that reads somewhere that it can update (a secret flag in the repo?) or does a “external” service trigger my local swupd (very unlikely). Just curious to know.
In short swupd reads a file which contains the official release (or from the equivalent mirror location). If it passes QA, all the content is already uploaded to the servers so can be rolled out very quickly from there.
I think it’s great for testing that these remain, as while they don’t pass QA, you could find out the exact version an issue starts occurring in which could cut out a number of packages if a couple of releases missed passing QA. But the benefit is almost entirely for developer/testing purposes and not for normal users.