oVirt 3.6.1 branch has been created
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
Hi I think it was premature. I still see a lot of bugs to be fixed in 3.6.1. See query: https://bugzilla.redhat.com/report.cgi?x_axis_field=bug_status&y_axis_field=status_whiteboard&z_axis_field=target_milestone&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&target_milestone=ovirt-3.6.1&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&n1=1&f1=status_whiteboard&o1=anywordssubstr&v1=docs%2Cnode&f2=flagtypes.name&o2=anywordssubstr&v2=&f3=noop&o3=noop&v3=&format=table&action=wrap And if looking only at blockers and exceptions I see 25 bugs still on new/assigned/post. https://bugzilla.redhat.com/report.cgi?x_axis_field=bug_status&y_axis_field=status_whiteboard&z_axis_field=target_milestone&no_redirect=1&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&target_milestone=ovirt-3.6.1&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&j_top=AND&n1=1&f1=status_whiteboard&o1=anywordssubstr&v1=docs%2Cnode&f2=flagtypes.name&o2=anywordssubstr&v2=blocker%2Cexception&f3=noop&o3=noop&v3=&f4=noop&o4=noop&v4=&format=table&action=wrap Why not to do the branching later, when we get it more stable or push bugs out of it? 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
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 ?
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
On Wed, Nov 18, 2015 at 4: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 ?
The branch is supposed to be the place where stabilization happen. The criteria is branch whenever a build is required. I've been asked to issue a build this morning so I branched. Too bad the request has been retired in the afternoon.
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
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
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?
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
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
On Wed, Nov 18, 2015 at 6: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.
Well, does it always work well for you? I didn't hear one good reason to do the branching now. So yes. I suggest you revert it (or give good reasons not to).
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
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
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.
can anyone clarify whether patches targeted for the ovirt 3.6.1 release should be backported to the ovirt-engine-3.6.1 branch at this point or not? we have several patches like that and we are not sure what to do with them. [I see that https://gerrit.ovirt.org/48709 was reverted [1], however the ovirt-engine-3.6.1 branch still exists] thanks in advance. [1] https://gerrit.ovirt.org/#/c/48816/ ----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Roy Golan" <rgolan@redhat.com>, "Yaniv Kaul" <ykaul@redhat.com>, "Tal Nisan" <tnisan@redhat.com>, "Piotr Kliczewski" <pkliczew@redhat.com> Cc: "devel" <devel@ovirt.org> Sent: Wednesday, November 18, 2015 11:23:27 AM Subject: Re: [ovirt-devel] oVirt 3.6.1 branch has been created
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.
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
On Mon, Nov 23, 2015 at 8:41 PM, Einav Cohen <ecohen@redhat.com> wrote:
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.
can anyone clarify whether patches targeted for the ovirt 3.6.1 release should be backported to the ovirt-engine-3.6.1 branch at this point or not? we have several patches like that and we are not sure what to do with them. [I see that https://gerrit.ovirt.org/48709 was reverted [1], however the ovirt-engine-3.6.1 branch still exists]
We're building 3.6.1 RC1 today, so https://gerrit.ovirt.org/48709 will be merged again today and 3.6.1 branch will be re-aligned to this point. I'll send an email with all the references so you'll know what's missing in 3.6.1.
thanks in advance.
[1] https://gerrit.ovirt.org/#/c/48816/
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Roy Golan" <rgolan@redhat.com>, "Yaniv Kaul" <ykaul@redhat.com>, "Tal Nisan" <tnisan@redhat.com>, "Piotr Kliczewski" <pkliczew@redhat.com> Cc: "devel" <devel@ovirt.org> Sent: Wednesday, November 18, 2015 11:23:27 AM Subject: Re: [ovirt-devel] oVirt 3.6.1 branch has been created
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
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
bugs 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
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Tue, Nov 24, 2015 at 8:41 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
On Mon, Nov 23, 2015 at 8:41 PM, Einav Cohen <ecohen@redhat.com> wrote:
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.
can anyone clarify whether patches targeted for the ovirt 3.6.1 release should be backported to the ovirt-engine-3.6.1 branch at this point or not? we have several patches like that and we are not sure what to do with them. [I see that https://gerrit.ovirt.org/48709 was reverted [1], however the ovirt-engine-3.6.1 branch still exists]
We're building 3.6.1 RC1 today, so https://gerrit.ovirt.org/48709 will be merged again today and 3.6.1 branch will be re-aligned to this point. I'll send an email with all the references so you'll know what's missing in 3.6.1.
origin/ovirt-engine-3.6.1 has been rebased on origin/ovirt-engine-3.6 at * ee96f2e - (HEAD -> ovirt-engine-3.6.1, origin/ovirt-engine-3.6.1) core: Bootable disk index considers CDROM on PPC (5 minutes ago) <Marek Libra> a bump patch for moving to 3.6.2 has been pushed to ovirt-engine-3.6 branch here: https://gerrit.ovirt.org/49054 a build patch will be pushed in a few minutes to ovirt-engine-3.6.1 branch. The build will start at 10:00 CET / 11:00 Israel time.
From now on, any patch targeted to 3.6.1 must be cherry-picked to ovirt-engine-3.6.1 branch. From now on only patches for blocker bugs are allowed on ovirt-engine-3.6.1 branch.
Thanks,
thanks in advance.
[1] https://gerrit.ovirt.org/#/c/48816/
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "Roy Golan" <rgolan@redhat.com>, "Yaniv Kaul" <ykaul@redhat.com>, "Tal Nisan" <tnisan@redhat.com>, "Piotr Kliczewski" <pkliczew@redhat.com> Cc: "devel" <devel@ovirt.org> Sent: Wednesday, November 18, 2015 11:23:27 AM Subject: Re: [ovirt-devel] oVirt 3.6.1 branch has been created
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
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
bugs 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
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Wed, Nov 18, 2015 at 11:33 AM, 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.
Due to Ci issue I had to move the branch from 3.6.1.x (which I used for avoiding confusion with the tags) to 3.6.1.
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (6)
-
Einav Cohen -
Martin Sivak -
Moti Asayag -
Oved Ourfali -
Roy Golan -
Sandro Bonazzola