On Mon, Jan 29, 2018 at 9:39 AM, Francesco Romani <fromani@redhat.com> wrote:
Hi all,
It is time again to reconsider branching out the 4.2 stable branch.
So far we decided to *not* branch out, and we are taking tags for ovirt
4.2 releases from master branch.
This means we are merging safe and/or stabilization patches only in master.
I think it is time to reconsider this decision and branch out for 4.2,
because of two reasons:
1. it sends a clearer signal that 4.2 is going in stabilization mode
2. we have requests from virt team, which wants to start working on the
next cycle features.
If we decide to branch out, I'd start the new branch on monday, February
5 (1 week from now).
The discussion is open, please share your acks/nacks for branching out,
and for the branching date.
I for myself I'm inclined to branch out, so if noone chimes in (!!) I'll
execute the above plan.
+1 from me, but FYI if not all projects or at least the important ones like ovirt-engine will do the same or add mapping from master to 4.2, like explained in the 4.2 thread on devel list,
Then CI won't really work for 4.2, as it will probably need always newer engine version or other pkgs that only exists in master flow.
--
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh
_______________________________________________
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
irc: eedri (on #tlv #rhev-dev #rhev-integ)