<div dir="ltr">Hi All,<div><br></div><div>I'm currently working to solve this issue.</div><div>I will update you when done :)</div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Best Regards,</div><div dir="ltr"><br></div><div dir="ltr">Shlomi Ben-David | Software Engineer <span style="font-size:small">| </span><span style="font-size:12.8px">Red Hat ISRAEL</span></div><div><span style="font-size:12.8px">Red Hat </span>Certified System Administrator | <span style="font-size:small">Red Hat Certified Engineer</span><span style="font-size:small"> </span><span style="font-size:12.8px"> </span></div><div dir="ltr">IRC: shlomibendavid <span style="font-size:small">(on #rhev-integ, #rhev-dev, #rhev-ci)</span><br><br>OPEN SOURCE - 1 4 011 && 011 4 1<br></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Aug 17, 2016 at 10:10 AM, 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">Hi all,<br>
<br>
We currently have a bot that automatically moves bugs from POST to MODIFIED<br>
if all linked patches on gerrit are merged.<br>
<br>
It happened to me personally several times that this was a wrong thing to do,<br>
either because a new patch was still needed but not pushed yet, or because<br>
an existing patch should have been back-ported to another branch and wasn't<br>
yet. Since I usually pay more attention to my bug in POST, I sometimes missed<br>
this and handled the missing patches (backports, usually) later than I could<br>
if left on POST.<br>
<br>
I have a feeling I am not the only one. So I suggest to stop doing this.<br>
<br>
I can think of several alternatives:<br>
<br>
1. Do nothing. I think that's reasonable - I think most people pay more<br>
attention to POST bugs anyway.<br>
<br>
2. Set needinfo on bug owner.<br>
<br>
3. Send some alert email to relevant people (bug owner, existing patches owners,<br>
perhaps others - e.g. reviewers of existing patches, perhaps those<br>
that actually reviewed, etc.). Need to think how to make it not too<br>
annoying for others but<br>
still effective also if owner is on long PTO or something like that. New flag<br>
doesn't have to be very specific - can be called something like 'attention<br>
needed' or something like that.<br>
<br>
4. Add a new flag for that and set it. This will allow easier<br>
filtering/reporting.<br>
<br>
What do you think?<br>
<span class="HOEnZb"><font color="#888888">--<br>
Didi<br>
______________________________<wbr>_________________<br>
Devel mailing list<br>
<a href="mailto:Devel@ovirt.org">Devel@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/devel</a><br>
</font></span></blockquote></div><br></div>