New issue tracker and architectural discussion


#1

EDIT: I want to clarify I posted this on my own; team opinions differ on how close we are on this.

Since the issue tracker was created: https://github.com/coreos/fedora-coreos-tracker/issues
We’ve been filing issues and hashing out some architectural choices there. There’s a high
level vision: we want to take a lot of the Container Linux experience, notably Ignition and
automatic updates, though we’ll use ostree and not update_engine. There are still beyond
that a whole lot of details.

I know things have seemed quiet, but I think we’re not too far away from having a first preview
of a release. In the background we’ve been putting a lot of work into getting Ignition working
for example, e.g.:

And there’s more going on; a big detail is how the build system works and its relationship to Fedora, etc. At this point we’d welcome people to join in on our issue tracker - particularly existing Container Linux and Atomic users interested in the details of the merger/transition.


#2

I think we’re not too far away from having a first preview of a release

Exciting, if this is still the case!

Expectations-wise, would folks working on the project be able to say whether a preview of Fedora CoreOS might be available for others to kick the tires on within a matter of weeks—or might it be closer to a matter of months?

At this point we’d welcome people to join in on our issue tracker - particularly existing Container Linux and Atomic users interested in the details of the merger/transition.

As a CL user for the past few years I definitely appreciate the effort you all have put into the new tracker, FAQ, discussion board, etc… reading through these resources is certainly starting to help better clarify the merger/transition for me, so, thanks :slight_smile:


#3

currently no ETA. Sorry. We are planning our first official release to coincide with Fedora 30. There will be something to download and play with before then, but that’s when we hope to have most kinks worked out.