Nir Soffer <nsoffer(a)redhat.com> writes:
On Mon, Jan 21, 2019 at 10:30 AM Milan Zamazal
> Hi, I'm going to make ovirt-4.3 Vdsm branch next week.
> If there are any very important reasons not to make it, please let me
We have several 4.3 features , , , that require lot of work.
There is also critical lvm bug  that require major changes .
Branching too early will make it harder and more risky to have the changes
Branching too late add risk from 4.4 work done on master, so we have to
There is also problem with ongoing work on Python 3, where it's
difficult to share, synchronize, and not-to-duplicate work by several
people when we can't merge patches. OTOH the same work could disrupt
finishing and backporting 4.3 patches.
OK, in this case of conflicting interests working hard on the storage
patches looks like the best way to resolve the problem :-). I'll keep
eye on progress of the work you mention below and let's discuss
branching again in about two weeks.
>  incremental backup - https://gerrit.ovirt.org/c/96216/
> this is only the API, we need to implement them
>  4k support:
>  https://bugzilla.redhat.com/1553133
>  https://gerrit.ovirt.org/q/topic:lvm-read-only+is:open