<div dir="ltr">indeed.<div>we need to decide here what automation we want (each flow has its cons & pros)</div><div><br></div><div>moving bugs from POST->MODIFIED</div><div> - pros</div><div> - bugs are not forgotten on POST and waiting for manual action, leaving possibility of not moving to ON_QA on a release even though they are fixed.</div><div><br></div><div> - cons</div><div> - bot can't know if bug is solved completely and more patches are coming.</div><div><br><br></div><div>solution:</div><div> - use bug-url ONLY in the main patch that when its merged then bug will move to MODIFIED, all other patches should use related-to: (we can ensure bug won't change status for related to patches)</div><div><br></div><div><br></div><div>moving MODIFIED->POST</div><div> - i think in any case we should stop doing this, and its the maintainer responsibility to move it back to POST if he didn't add all patches.</div><div> - adding a comment will help the bug owner know about this issue.</div><div><br></div><div>e.</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 17, 2015 at 10:47 AM, David Caro <span dir="ltr"><<a href="mailto:dcaro@redhat.com" target="_blank">dcaro@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 11/17 10:44, Yedidyah Bar David wrote:<br>
> See e.g. [1]. Patch was merged to master only (not to 3.6 branch), bug<br>
> was moved to modified. When I later pushed the patch to 3.6, it<br>
> correctly moved it back to POST. Not sure we should even automatically<br>
> move to modified if merged to 3.6, because there might be other<br>
> changes needed for that bug - it might be best to let the owner to<br>
> decide.<br>
<br>
</span>The issue here is that there's no way for the hooks to know that you will be<br>
pushing more patches, so when it saw that there were no more open patches it<br>
moved the bug to MODIFIED. Is there any reason why you did not open the patches<br>
first?<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> [1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1282397" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1282397</a><br>
><br>
> Best,<br>
> --<br>
> Didi<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>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
David Caro<br>
<br>
Red Hat S.L.<br>
Continuous Integration Engineer - EMEA ENG Virtualization R&D<br>
<br>
Tel.: <a href="tel:%2B420%20532%20294%20605" value="+420532294605">+420 532 294 605</a><br>
Email: <a href="mailto:dcaro@redhat.com">dcaro@redhat.com</a><br>
Web: <a href="http://www.redhat.com" rel="noreferrer" target="_blank">www.redhat.com</a><br>
RHT Global #: 82-62605<br>
</font></span><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></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Eyal Edri<br>Supervisor, RHEV CI<br>EMEA ENG Virtualization R&D<br>Red Hat Israel<br><br>phone: +972-9-7692018<br>irc: eedri (on #tlv #rhev-dev #rhev-integ)</div>
</div>