On Wed, Dec 2, 2020 at 12:31 PM Neal Gompa <ngomp...@gmail.com> wrote: > This is a fair point. I've personally been very annoyed about how > little Fedora CoreOS integrates with the rest of the Fedora Project. > One very broken consequence of Fedora CoreOS working this way is that > they basically *don't* participate in Changes discussions and just do > things differently without warning or documentation. This has led to > problems when Fedora CoreOS differs from the rest of Fedora in core, > fundamental ways. This has even happened unintentionally, where Fedora > CoreOS accidentally deviated from Fedora (and RHEL CoreOS!) by using > the wrong variant of iptables: > https://github.com/coreos/fedora-coreos-tracker/issues/676
We do look over every Fedora Changes that come through and evaluate how we need to adapt FCOS for them. I agree we could do a better job at providing more timely feedback to change owners and the community (thinking about the recent rpmdb backend change for example). Part of it I think is that we do not yet have a rawhide stream which would expose us to all these changes earlier (it's on the radar though!). But to be clear, the intent is always to match Fedora whenever possible. Due to our update model, we have to be extremely careful about these changes, and sometimes that means that FCOS lags behind a bit in getting them. The iptables example was an unfortunate slip up; ordinarily this would've been part of the f32 rebase just like the rest of Fedora. > Additionally, to the point about their tooling: there's been a bunch > of effort to plug OSBuild based image builds into our normal > infrastructure, and given that even Fedora IoT Edition can > successfully be produced through that pipeline, I would think that we > should have Fedora CoreOS transition to it. There's a lot more effort > going around OSBuild within the project as a whole, and it's much more > likely that we'll be able to incorporate that into the general > infrastructure in a way that makes it traceable and actionable within > and outside the project. I agree build tooling is an important part of the picture. Both teams of coreos-assembler and osbuild are aware of the overlap that exists and we do plan to discuss this further. Though this is not something we are likely to tackle in any serious way anytime soon. So for the purposes of this discussion, I hope we can put this aside. We do run our builds in CentOS CI, but we're open to integrating with Fedora processes in any way necessary. For example, we recently added informational fedmsgs when builds and releases happen as Clement linked to above. _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
