Fedora CoreOS will include a variety of new features and components, including: a multiple-stream structure with promotions and backported fixes, staged update rollout with reboot coordination, the Ignition 3.0 spec, live PXE support, metrics, a Fedora CoreOS config transpiler, and migration tooling from Container Linux. It will also need to support much of the functionality and use cases of Container Linux. With the magnitude of new work going into Fedora CoreOS, it would be useful to have a public preview period during which we can fix bugs and make breaking changes before the OS is deployed into production use.
A preview period could work like this:
- The initial preview release would occur sometime after the release of F30.
- Soon after F31 is released, Fedora CoreOS would rebase onto it via the usual
testing -> stable promotion process.
- Soon after, Fedora CoreOS would be declared stable and thus suitable for production use.
The preview release would aim to provide a working OS that is ready for broader use and feedback. While it should give a good sense of what Fedora CoreOS will be, it would not be feature-complete, well-documented, or production-ready. There would undoubtedly be environments or use cases where the OS will not work properly. We'd also want to preserve the ability to make breaking changes to the OS if necessary.
Implications for Fedora Atomic Host
Fedora Atomic Host would not be rebased onto Fedora 30. It would continue to have two-week releases through the lifetime of F29, and then would be EOL.
Implications for Container Linux
Container Linux EOL would occur ~6 months after Fedora CoreOS goes stable. We'd want to announce a concrete EOL date with plenty of advance notice. Migration tooling would likely not be complete for the initial preview release, but would improve throughout the preview period and be ready for production use by the stable release.
Fedora CoreOS will include a variety of new features and components, including: a multiple-stream structure with promotions and backported fixes, staged update rollout with reboot coordination, the Ignition 3.0 spec, live PXE support, metrics, a Fedora CoreOS config transpiler, and migration tooling from Container Linux. It will also need to support much of the functionality and use cases of Container Linux. With the magnitude of new work going into Fedora CoreOS, it would be useful to have a public preview period during which we can fix bugs and make breaking changes before the OS is deployed into production use.
A preview period could work like this:
testing->stablepromotion process.The preview release would aim to provide a working OS that is ready for broader use and feedback. While it should give a good sense of what Fedora CoreOS will be, it would not be feature-complete, well-documented, or production-ready. There would undoubtedly be environments or use cases where the OS will not work properly. We'd also want to preserve the ability to make breaking changes to the OS if necessary.
Implications for Fedora Atomic Host
Fedora Atomic Host would not be rebased onto Fedora 30. It would continue to have two-week releases through the lifetime of F29, and then would be EOL.
Implications for Container Linux
Container Linux EOL would occur ~6 months after Fedora CoreOS goes stable. We'd want to announce a concrete EOL date with plenty of advance notice. Migration tooling would likely not be complete for the initial preview release, but would improve throughout the preview period and be ready for production use by the stable release.