Re: [ovirt-devel] oVirt 3.6.1 branch has been created

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:

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?

+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