
It is not about the cherry-pick button. It is about CI being very slow and the need to execute the jobs again and again every time something else is merged first because we have to constantly rebase to be able to submit. This whole thing accumulates into such mess that we missed couple of verified 3.6.0 patches just because they could not be merged on time. We already have that on master (where the slow CI was disabled for this reason) and on the 3.6 branch. Adding a third branch with checks like that means it is almost a miracle if a patch makes it on time. Martin On Wed, Nov 18, 2015 at 5:23 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Wed, Nov 18, 2015 at 4:27 PM, Roy Golan <rgolan@redhat.com> wrote:
On Wed, Nov 18, 2015 at 5:23 PM, Moti Asayag <masayag@redhat.com> wrote:
On Wed, Nov 18, 2015 at 1:33 PM, Oved Ourfali <oourfali@redhat.com> wrote:
Hi
I think it was premature.
I still see a lot of bugs to be fixed in 3.6.1. See query:
And if looking only at blockers and exceptions I see 25 bugs still on new/assigned/post.
Why not to do the branching later, when we get it more stable or push bugs out of it?
+1, are there any stabilization criteria to determine when a code base is considered stabilized enough for branching ?
Guys the overhead of cherry picking isn't small. Why CI issues promoted that?
CI issues just asked to rename from 3.6.1.x to 3.6.1. Branch creation has nothing to do with CI requests. Guys, if hitting cherry-pick button on gerrit web ui costs to much feel free to revert https://gerrit.ovirt.org/48709 and delete ovirt-engine-3.6.1 branch. Let me know when you'll be ready to branch.
Thanks, Oved
On Wed, Nov 18, 2015 at 12:33 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Hi, just an heads up we branched for 3.6.1 stabilization this morning. If you have patches targeted to 3.6.1 you now need to cherry-pick them to 3.6.1 branch too. A build is scheduled for today at 2 PM TLV time.
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ 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
-- Regards, Moti
_______________________________________________ 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
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel