Sorry guys - a typo, it was branched from ovirt-engine-4.0 obviously, no worries and thanks for noticing :)

On Tue, Aug 30, 2016 at 3:23 PM, Eyal Edri <eedri@redhat.com> wrote:

On Tue, Aug 30, 2016 at 3:01 PM, Martin Perina <mperina@redhat.com> wrote:

On Tue, Aug 30, 2016 at 1:26 PM, Tal Nisan <tnisan@redhat.com> wrote:

Hi everyone,

We've created ovirt-engine-4.0.4 branch this morning from the 4.0.3 branch.

​From 4.0.3? It was expected that ovirt-engine-4.0.4 branch will be based on ovirt-engine-4.0​ ...

I agree the 4.0.4 should be branched from 4.0 branch not 4.0.3.

4.0.3 was only for async and was branched out of 4.0.2

 

If 4.0.4 is branched from 4.0.3 then we would need to backport patches from all MODIFIED bugs (currently 104) to ovirt-engine-4.0.4 branch. I think that is waste of time and resources ...

From now on 4.0.4 Engine patches will have to be backported to the new branch after being backported to the ovirt-engine-4.0 branch.

Engine 4.0.5 patches can now be backported to ovirt-engine-4.0 branch.

Tal.

_______________________________________________
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

--

Eyal Edri
Associate Manager

RHV DevOps
EMEA ENG Virtualization R&D
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)