[ovirt-devel] Ending support for 3.x engines on master
Nir Soffer
nsoffer at redhat.com
Mon Jun 20 17:53:58 UTC 2016
On Mon, Jun 20, 2016 at 7:49 PM, Nir Soffer <nsoffer at redhat.com> wrote:
> On Sun, Jun 19, 2016 at 3:40 PM, Dan Kenigsberg <danken at redhat.com> wrote:
>> On Sun, Jun 19, 2016 at 02:13:40PM +0300, Nir Soffer wrote:
>>> Hi all,
>>>
>>> We should not support now Engine 3.5 with ovirt 4.0, but vdsm still
>>> accept 3.5 engines - I guess we forgot to disable it in 4.0.
>>
>> Correct. There was a moment in time where we considered supporting 3.5
>> as well.
>
> Ok, so we can remove now 3.5 support, and backport it to 4.0.
Posted https://gerrit.ovirt.org/59504 , please ack.
>
>>> In 4.1, I don't think we should support any 3.x Engine - otherwise we
>>> will have to waste time maintaining old apis and infrastructure, instead
>>> of adding new features that matter to our users.
>>
>> Do you have a list of old APIs you'd like to throw away? We've killed a
>> few in 4.0, and
>> $ git grep REQUIRED_FOR
>> is not huge.
>
> I don't think we have many verbs to remove, it is mainly about rotten
> infrastructure that we can delete or simplify.
>
> Nir
>
>>
>>>
>>> I suggest we disable now support for 3.x engines.
>>>
>>> Please see Eli patch:
>>> https://gerrit.ovirt.org/59308
>>>
>>> Thoughts?
>>
>> +1, but let's see if ydary/mgoldboi think we should keep 3.6.
More information about the Devel
mailing list