[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic] OpenStack Magnum concerns about Project Atomic

On Wed, Feb 24, 2016 at 11:40:10AM -0500, Matt Micene wrote:
> CoreOS is a standalone distro, and can move at whatever speed for whatever
> component they like.  Our packages move at the speed of Fedora.  The Atomic
> members may be maintainers of a component, but if Fedora decides that, for
> example, docker 1.10 is a breaking change that needs to wait until F24,
> there's not a lot we can do about it for a F23 based Atomic Host.

This is basically true, but we're also trying to figure out how to do
it better. There are several options:

* Simply packaging these things for parallel existence, like docker110
  (not my preference, but easily done with no changes to the way we do 

* Putting packages like this in updates-testing, but *not* pushing them
  to stable; pulling from updates-testing for the Atomic tree compose

* Allow Atomic f23 to pull selected packages from the f24 branch. This
  won't work for all packages, of course, due to dependencies, but will
  for many.

* Allowing Atomic to draw from a Copr instead of the main repository.
  Right now, Copr is an experimental service and I'm not ready to
  recommend this, but it's a future possibility. (To avoid this
  becoming a crazy fork, the policy could be that the Copr itself must
  be composed from packages in Rawhide.)

Longer term, I'm interested in seeing source-to-image for approved
upstream code as native Fedora deliverables, in addition to RPMs — so
this could be an entirely parallel stream.

Matthew Miller            mattdm mattdm org             <http://mattdm.org/>
Fedora Project Leader  mattdm fedoraproject org  <http://fedoraproject.org/> 

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]