[ovirt-devel] Re: code merges in ovirt-engine repo
On 14 Jul 2020, at 12:11, Yedidyah Bar David <didi(a)redhat.com>
wrote:
On Tue, Jul 14, 2020 at 11:43 AM Michal Skrivanek
<michal.skrivanek(a)redhat.com> wrote:
>
> Hi all,
> we’re moving to 4.4.z development now and we need to keep a closer eye on automation
results and making sure the build is not broken. For these reasons we’re considering
moving to a similar model as vdsm, having a smaller set of people with merge rights to
make sure the patches get in in the right order and they meet our sanity standards (OST,
bug’s TM)
> Any objections/comments?
Any reason to not simply branch 4.4? And have the branch maintained by
the stable branches maintainers?
just the sheer amount of backports needed (every patch). Doesn’t sound worth the effort of
posting and reviewing(even if just formally) everything twice.
--
Didi