On 04.11.2014 09:47, Fabian Deutsch wrote:
----- Original Message -----
> On Sun, Sep 14, 2014 at 03:17:39PM +0300, Itamar Heim wrote:
>> On 09/12/2014 03:22 PM, Itamar Heim wrote:
>>> With oVirt 3.5 nearing GA, time to ask for "what do you want to see in
>>> oVirt 3.6"?
>> Even the short list of items mentions so far are big features we would need
>> to do justice with.
>> this means probably a slightly longer cycle than the 6 months we currently
> We're not so good in keeping up with deadlines - our recent 3.5 version
> slipped for 2.5 months past the original plan. With longer cycles, this
> is even harder to control.
> Can we instead break the "heavier" features to smaller phases, that are
> easier to maintain, and deliver the complete feature in 3.7?
yep, I think this is a good idea to get control over the big features.
Me too, for that matter. I think json rpc was a major thing to do witch
went well; but maybe drew resources from other features and testing.
But maybe new features do not need to be scrubbed but implemented later
on for upgrades? For instance, some software vendors allow new features
for X.0 releases only for new installations. Only after they are
confirmed working regression - free a X.1 version is released witch
enables upgrades from X-1 (existing customers).
Bottom line, I hope for planned 3.6 features like SR-IOV and pci
passthrough/vfio will not be postponed :)
>> with many of the features requiring way newer versions of some of the
>> components, I think we should plan for "3.6 cluster" to require an
>> (expecting even 7.1 to be out before we release oVirt 3.6).
>> so i want us to plan for:
>> - oVirt 3.6 supports .el6 and .el7 hosts in 3.5 cluster (and for fedora
>> - fc20?)
>> - oVirt 3.6 supports .el7 in 3.6 cluster (and for fedora - fc21?)
> Users mailing list
Users mailing list
m box bewegtbild GmbH
Geschäftsführer: Martin Retschitzegger / Michaela Göllner
Handeslregister: Amtsgericht Charlottenburg / HRB 112767