On 03/16/2015 11:48 PM, Alon Bar-Lev wrote:
----- Original Message -----
From: "Itamar Heim" <ih...@redhat.com>
To: "Sahina Bose" <sab...@redhat.com>, "Dan Kenigsberg" <dan...@redhat.com>,
devel@ovirt.org
Sent: Monday, March 16, 2015 11:41:36 PM
Subject: Re: [ovirt-devel] el6 future in ovirt-3.6
On 03/16/2015 06:02 PM, Sahina Bose wrote:
On 03/16/2015 03:28 PM, Dan Kenigsberg wrote:
Current master branch of vdsm (destined for our 3.6 release) uses el7 as
its main platform. New features are expected to be available only on el7
(and modern Fedoras) but not on el6.
On el6, vdsm still builds, runs, and exports clusterLevel <= 3.5, with
no feature loss relative to 3.5. This has been done per gluster request.
However, maintaining this furhter as high costs: we keep testing el6, we
need to make sure nothing breaks there, and there's a lot of legacy code
that we could start deleting.
Sahina, would you explain (again... sorry for not recalling the details)
why ovirt-3.6's vdsm should keep running on el6? I'd like to see if
there's a nother means to solve the underlying gluster issue.
This was only because downstream gluster + vdsm would continue to be
supported on RHEL 6.
is there an expected date at which new features would be .el7 only, so
.el6 support can be dropped upstream?
there is no reason to drop anything from upstream if it is to be supported. it
will only create overhead for product support. we have long on going effort is
to reduce diff while you keep pushing for fork. it always turned out to be
incorrect decision. please learn from experience.
I asked when they plan to drop support, so we can drop unneeded code.
Regards,
Dan.
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
