We chatted about this in the community meeting today. I know you know
this, but for the benefit of everyone: Fedora CoreOS does rolling
releases and so doesn't follow the same release cycles. That said, we
thought it'd be a good opportunity to highlight that fact and also
talk about some of the things we've been working on (even if they're
not strictly gated on f34). Pasting the doc we typed up collectively
(formatted as markdown):
Fedora CoreOS has three streams (`stable`, `testing`, and `next`)
which operate on a rolling basis. This means that Fedora 34 will
automatically reach these streams after GA without any intervention by
users. Our `branched` development stream is currently tracking Fedora
CoreOS based on Fedora 34.
Here are some highlights of recently added features in Fedora CoreOS:
- The `/boot` partition is now mounted read-only. This continues the
work to protect more of the OS from accidental damage.
- It is now possible to configure boot disk RAID 1 mirroring via
Ignition:
https://docs.fedoraproject.org/en-US/fedora-coreos/storage/#_reconfigurin...
- Better introspection into the state of Zincati (the update agent)
from `rpm-ostree status`.
- Initial (non-automatic) support for updating the bootloader:
https://docs.fedoraproject.org/en-US/fedora-coreos/bootloader-updates/
We are also working on some exciting new features:
- Support for specifying kernel arguments via Ignition:
https://github.com/coreos/ignition/issues/1168
- Move to cgroup v2 by default:
https://github.com/coreos/fedora-coreos-tracker/issues/292
If you'd like to help test the `branched` development stream, download
the artifacts from [the development build
browser](https://builds.coreos.fedoraproject.org/browser?stream=branched).
You can report issues in [the Fedora CoreOS issue
tracker](https://github.com/coreos/fedora-coreos-tracker).