<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 17, 2015 at 11:11 AM, Yedidyah Bar David <span dir="ltr"><<a href="mailto:didi@redhat.com" target="_blank" onclick="window.open('https://mail.google.com/a/https://mail.google.com/mail/u/1/?zx=h6bgwpurpc3#inbox/mail/?view=cm&tf=1&to=didi@redhat.com&cc=&bcc=&su=&body=','_blank');return false;">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 Tue, Nov 17, 2015 at 10:54 AM, Eyal Edri <<a href="mailto:eedri@redhat.com" onclick="window.open('https://mail.google.com/a/https://mail.google.com/mail/u/1/?zx=h6bgwpurpc3#inbox/mail/?view=cm&tf=1&to=eedri@redhat.com&cc=&bcc=&su=&body=','_blank');return false;">eedri@redhat.com</a>> wrote:<br>
> indeed.<br>
> we need to decide here what automation we want (each flow has its cons &<br>
> pros)<br>
><br>
> moving bugs from POST->MODIFIED<br>
> - pros<br>
> - bugs are not forgotten on POST and waiting for manual action,<br>
> leaving possibility of not moving to ON_QA on a release even though they are<br>
> fixed.<br>
<br>
</span>I think it's still a bit risky and should be left for a human. At least as long<br>
as we do not do TDD.<br>
<span class=""><br>
><br>
> - cons<br>
> - bot can't know if bug is solved completely and more patches are<br>
> coming.<br>
><br>
><br>
> solution:<br>
> - use bug-url ONLY in the main patch that when its merged then<br>
> bug will move to MODIFIED, all other patches should use related-to: (we can<br>
> ensure bug won't change status for related to patches)<br>
<br>
</span>I can live with this, but as I wrote in another mail in this thread, I think<br>
that's a bit overloading the meaning of Related-To.<br>
<span class=""><br>
><br>
><br>
> moving MODIFIED->POST<br>
> - i think in any case we should stop doing this, and its the<br>
> maintainer responsibility to move it back to POST if he didn't add all<br>
> patches.<br>
<br>
</span>Really? Do you see any risk in moving to POST?<br></blockquote><div><br></div><div>yes. we talked in the past about bots moving statues back,</div><div>and it should be left for human - i don't see a reason why this should be different.</div><div>but we can bring it up for discussion, a change in hooks affects everyone and </div><div>not to be decided on a mail thread</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888">--<br>
Didi<br>
</font></span></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></div>