The output of the command:
ostree remote refs fedora | grep x86_64/silverblue
shows:
fedora:fedora/37/x86_64/silverblue
fedora:fedora/38/x86_64/silverblue
fedora:fedora/rawhide/x86_64/silverblue
I thought Rawhide means the next version which is not released yet. If 37 is the current version, what is the difference between 38 and Rawhide?
Edit: typo.
We just reached a development milestone — the branch. F38 is now split from Rawhide, leading up to the beta and final release. Rawhide is now what will become F39.
Right now, the differences are likely small, but they will get wider and wider as Rawhide continues to move ahead.
@mattdm Hi, I have ran Silverblue Beta quite a few times before, but I wanted to know: at which point between branching and the Beta milestone being achieved is that it becomes relatively safe to jump into the new unstable version? (I usually report any bugs I find, so it is not a big issue if a few small ones pop up).
From the schedule, the beta is targeted for release on March 21st.
Of course, “relatively safe” is always relative, but that’s probably the point to aim for. Personally, I’ve been upgrading most of my systems about a month before that, at the “Beta Freeze” checkpoint, and I’ve had no more than the “small bugs” experience so far. But we do that freeze for a reason — it’s not what we really recommend for users.
I guess one way to put it might be: how far do you want to venture into the “I’m a tester!” field? Or, would you rather stay firmly behind the safety fences?
As a home user, unless I am trying to test installation / booting issues, I will look for “Beta Freeze” to start testing the next release. As the feature set should be relatively complete by that milestone.
It does seem like we could find some way to signal this better in the ostree output. Currently, it’s not obvious at all that that’s not a released release.
This is pretty well explained in the documentation for Fedora rawhide and branched releases and Fedora update policy.