<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 19 Jul 2016, at 12:15, Eyal Edri <<a href="mailto:eedri@redhat.com" class="">eedri@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">This happened because you used the same bug for master and 4.0.</div></div></blockquote><div><br class=""></div>right, but that’s the regular state of things because upstream there is no separate bug for master vs current version</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="">The Gerrit hook doesn't verify status between major versions, only inside a single version (for e.g, it would not move to modified if you needed to backport to 4.0.1 and the target milestone was 4.0.1).</div><div class="">I'm not sure how we can tackle this, because master has no meaning in bugzilla, it doesn't correlate to a version.</div><div class=""><br class=""></div><div class="">One think I can think of, is NOT to move bugs to MODIFIED is a patch was merged on master branch... , will that help? </div></div></div></blockquote><div><br class=""></div>I’m not sure if it’s better because before 4.1 is branched the master development is for 4.1 bugs.</div><div>It would make sense to differentiate based on whether a branch for that TM version exists or not, so in your above example since the bug has TM 4.0.x and there is a 4.0 branch it would wait for a backport</div><div><br class=""></div><div>Thanks,</div><div>michal</div><div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Tue, Jul 19, 2016 at 8:07 AM, Michal Skrivanek <span dir="ltr" class=""><<a href="mailto:mskrivan@redhat.com" target="_blank" class="">mskrivan@redhat.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Example in bug <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1357440" rel="noreferrer" target="_blank" class="">https://bugzilla.redhat.com/show_bug.cgi?id=1357440</a><br class="">
It doesn't take into account branches<br class="">
<br class="">
Thanks,<br class="">
michal<br class="">
</blockquote></div><br class=""><br clear="all" class=""><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class="">Eyal Edri<br class="">Associate Manager</div><div class="">RHEV DevOps<br class="">EMEA ENG Virtualization R&D<br class="">Red Hat Israel<br class=""><br class="">phone: +972-9-7692018<br class="">irc: eedri (on #tlv #rhev-dev #rhev-integ)</div></div></div></div></div>
</div>
</div></blockquote></div><br class=""></body></html>