----- Original Message ----- > From: "Perry Myers" <[email protected]> > To: "Dan Kenigsberg" <[email protected]> > Cc: [email protected], "Cole Robinson" <[email protected]> > Sent: Wednesday, April 4, 2012 4:29:41 PM > Subject: Re: oVirt 3.1 targeted release platform > > On 04/04/2012 03:41 PM, Dan Kenigsberg wrote: > > On Wed, Apr 04, 2012 at 01:14:15PM -0400, Carl Trieloff wrote: > >> > >> > >> From a users perspective, it would be best for it to work on both > >> 16 & > >> 17 for a period of time.
anything we can do to enabled F16 and not require F17 will ease the transition. > > > > I believe that this makes "it" a "them" - at lease for vdsm this > > would > > require two rpms built and QAed. I hope we can avoid that, and > > release > > only one stack, preferably over f17. > > What if we got virt-preview updated again so that it contained the > right > packages so that the same version of vdsm would work on both: > > * f16 + virt_preview > * f17 > > Then we can have oVirt Node built based on f16 + virt_preview for > now, > and eventually move to pure f17. > > Dave/Cole, is updating virt-preview something you guys can help with? > > Perry > > > Note that even though vdsm's HEAD requires stuff that is out of > > f16, > > the vdsm team could produce stable vdsm builds for whatever > > platform > > that we choose. > > _______________________________________________ > > Arch mailing list > > [email protected] > > http://lists.ovirt.org/mailman/listinfo/arch > > _______________________________________________ > Arch mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/arch > _______________________________________________ Arch mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/arch
