<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 10, 2018 at 3:37 PM, Nigel Babu <span dir="ltr"><<a href="mailto:nigelb@redhat.com" target="_blank">nigelb@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello folks,<br><br>We now have <a href="http://review.gluster.org" target="_blank">review.gluster.org</a> as an external tracker on Bugzilla. Our current automation when there is a bugzilla attached to a patch is as follows:<br><br>1. When a new patchset has "Fixes: bz#1234" or "Updates: bz#1234", we will post a comment to the bug with a link to the patch and change the status to POST. 2. When the patchset is merged, if the commit said "Fixes", we move the status to MODIFIED.<br></div></blockquote><div><br></div><div>- I don't see a need for a comment if you add the external tracker (as suggested below).</div><div>- You really need some complex (but doable!) logic to look at the branch where the commit took place and the target release in Bugzilla to correctly move to MODIFIED state.</div><div>(there's also a corner case where multiple patches are needed for a bug, btw. Need to see all patches were merged, etc. before moving to MODIFIED).</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br>I'd like to propose the following improvements:<div>1. Add the Gerrit URL as an external tracker to the bug.</div><div>2. When a patch is merged, only change state of the bug if needed. If there is no state change, do not add an additional message. The external tracker state should change reflecting the state of the review.</div><div>3. Assign the bug to the committer. This has edge cases, but it's best to at least handle the easy ones and then figure out edge cases later. The experience is going to be better than what it is right now.<br></div><div><br>Please provide feedback/comments by end of day Friday. I plan to add this activity to the next Infra team sprint that starts on Monday (Sep 17).<br><br>--<br>nigelb</div></div>
<br>______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">https://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br></blockquote></div><br></div></div>