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.
This the only reason to branch out - "next cycle features" should be part of 4.2 as well?
Do other teams also plan to push new features to 4.2 that are not stable yet?
If not, I don't see any reason to branch out or backport "not stable" patches to 4.2 branch. We can keep it stable and avoid this branch-out unless we want to add new big feature that might cause regression in current stable 4.2 code.
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.
--
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