<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 17, 2017 at 5:36 PM, Mohammed Rafi K C <span dir="ltr"><<a href="mailto:rkavunga@redhat.com" target="_blank">rkavunga@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF"><span class="gmail-">
<p><br>
</p>
<br>
<div class="gmail-m_-5041974437840246430moz-cite-prefix">On 08/17/2017 05:07 PM, Nigel Babu
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>This change is taking the first step towards implementing
those ideas. One of the major blockers to implementing them
was that it was difficult to grant easy access to change the
hook. Granting production access to Gerrit is next to
impossible unless you really know what you're doing.</div>
<div><br>
</div>
<div>We'll not increase the scope *right now* to include
automating the entire bug workflow.<br>
</div>
</div>
</blockquote>
<br></span>
Cool. If I understand correctly , once we have the jenkins job in
place, we can resume the work done by Manikandan . is that right ?<br></div></blockquote><div><br></div><div>Yes. The Jenkins job is in place precisely to facilitate the work that Manikandan and Nandaja started in much nicer way.<br></div></div><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">nigelb<br></div></div>
</div></div>