On Fri, Mar 13, 2015 at 04:35:45PM -0500, Ian McLeod wrote: > > So the Atomic spins would be $current + the updates-testing > > packages we care about (and have tested / have some influence > > over). That spin would then be copied to the mirrors and we'd be > > able to link to it. > Actually, the idea is that Atomic spins would be $current + updates > (not testing), coupled with "updates" being more actively and > aggressively managed by those involved with Atomic. As I understand it, the concern here was possible wish for changes in something not part of the collection of software unique to Atomic. That is, if kubernetes needs to be updated, that's probably no big deal because at least as of now, Atomic is the main reason it's in the distro at all. And of course that's even more so for rpm-ostree and the `atomic` command itself. But it's a little less true for Docker, which is also important for developer workstations and possibly for Fedora Server. The other examples I've heard are the kernel and systemd — possibly some new features would be desired. I think the kernel is actually no problem here: the Fedora kernel team has a policy of following upstream closely, even updating in the $current and $current-1 releases. However, it's more unclear with systemd, and if newer systemd features are needed in $current we'll need to work closely with the systemd team. I don't think that will be a problem (and particularly, I think the systemd update example is mostly theoretical, right?), but it's definitely something to plan for _before_ we end up in a corner. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
