<div dir="ltr">It makes life easier for everyone when automation moves the bug to MODIFIED, if the work is not done then the developer can always move it back to POST like we sometimes do.<div>In any way, when a 3.6.3 bug is merged in 3.6.3 it should be moved to MODIFIED, not a second before</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 28, 2016 at 12:23 PM, Yedidyah Bar David <span dir="ltr"><<a href="mailto:didi@redhat.com" target="_blank">didi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Jan 28, 2016 at 10:59 AM, Eyal Edri <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>> wrote:<br>
><br>
><br>
> On Thu, Jan 28, 2016 at 10:23 AM, Yedidyah Bar David <<a href="mailto:didi@redhat.com">didi@redhat.com</a>><br>
> wrote:<br>
>><br>
>> On Thu, Jan 28, 2016 at 10:08 AM, Eyal Edri <<a href="mailto:eedri@redhat.com">eedri@redhat.com</a>> wrote:<br>
>> > Maybe we should change the logic on moving bugs to MODIFIED,<br>
>> > Now that we moved to the version branch.<br>
>> ><br>
>> > Tal - any thoughts on a logic that SHOULD move bugs to MODIFIED that<br>
>> > we'll<br>
>> > be sure its OK?<br>
>><br>
>> Repeating myself from a previous discussion: I think we should never move<br>
>> bugs from POST to MODIFIED. Only a developer can know if it's indeed<br>
>> ready,<br>
>> or another patch is still needed but was not yet pushed. I think it's<br>
>> safer<br>
>> to miss bugs left on POST although they could have been moved to MODIFIED,<br>
>> than the opposite - move to MODIFIED bugs that actually require more work.<br>
>><br>
><br>
> You're optimistic that bugs will not stay on POST, we've done it in the<br>
> past.<br>
> This has a bigger risk of bugs getting left behind on POST and increasing<br>
> the amount of<br>
> bugs that are not verified on time.<br>
><br>
> Its the easiest solution to drop this bot, but i belive it will do more<br>
> damage than good.<br>
<br>
</span>Perhaps, then, run it once a day and move to MODIFIED only if last patch<br>
was merged at least X hours ago? Hopefully developers will not wait more<br>
than X before pushing an additional patch for the same bug if needed.<br>
<br>
Of course, we then also have to fix the issue starting current thread.<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
>><br>
>> ><br>
>> > e.<br>
>> ><br>
>> > On Thu, Jan 28, 2016 at 10:03 AM, Tal Nisan <<a href="mailto:tnisan@redhat.com">tnisan@redhat.com</a>> wrote:<br>
>> >><br>
>> >> After merging a patch for a 3.6.3 bug on the ovirt-engine-3.6 branch<br>
>> >> the<br>
>> >> bug is moved to MODIFIED, since the 3.6.3 branch was opened yesterday<br>
>> >> the<br>
>> >> bug should stay in POST until merged in ovirt-engine-3.6.3 branch as<br>
>> >> well<br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> Infra mailing list<br>
>> >> <a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
>> >> <a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
>> >><br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > Eyal Edri<br>
>> > Associate Manager<br>
>> > EMEA ENG Virtualization R&D<br>
>> > Red Hat Israel<br>
>> ><br>
>> > phone: <a href="tel:%2B972-9-7692018" value="+97297692018">+972-9-7692018</a><br>
>> > irc: eedri (on #tlv #rhev-dev #rhev-integ)<br>
>> ><br>
>> > _______________________________________________<br>
>> > Infra mailing list<br>
>> > <a href="mailto:Infra@ovirt.org">Infra@ovirt.org</a><br>
>> > <a href="http://lists.ovirt.org/mailman/listinfo/infra" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman/listinfo/infra</a><br>
>> ><br>
>><br>
>><br>
>><br>
>> --<br>
>> Didi<br>
><br>
><br>
><br>
><br>
> --<br>
> Eyal Edri<br>
> Associate Manager<br>
> EMEA ENG Virtualization R&D<br>
> Red Hat Israel<br>
><br>
> phone: <a href="tel:%2B972-9-7692018" value="+97297692018">+972-9-7692018</a><br>
> irc: eedri (on #tlv #rhev-dev #rhev-integ)<br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Didi<br>
</font></span></blockquote></div><br></div>