<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">(gah, hit send too early)</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">... If we decide to stay with RB, that will need to be fixed.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 21 September 2016 at 09:53, Menno Smits <span dir="ltr"><<a href="mailto:menno.smits@canonical.com" target="_blank">menno.smits@canonical.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"><div class="gmail_default" style="font-family:verdana,sans-serif">Some of us probably got a little excited (me included). There should be discussion and a clear announcement before we make a signigicant change to our process. The tech board meeting is today/tonight so we'll discuss it there as per Rick's email. Please contribute to this thread if you haven't already and have strong opinions either way on the topic.<br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Interestingly our Github/RB integration seems to have broken a little since Github made these changes. The links to Reviewboard on pull requests aren't getting inserted any more. If we decide to stay with RB </div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 21 September 2016 at 05:54, Rick Harding <span dir="ltr"><<a href="mailto:rick.harding@canonical.com" target="_blank">rick.harding@canonical.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">I spoke with Alexis today about this and it's on her list to check with her folks on this. The tech board has been tasked with he decision, so please feel free to shoot a copy of your opinions their way. As you say, on the one hand it's a big impact on the team, but it's also a standard developer practice that not everyone will agree with so I'm sure the tech board is a good solution to limiting the amount of bike-shedding and to have some multi-mind consensus. <br></div><div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Sep 20, 2016 at 1:52 PM Katherine Cox-Buday <<a href="mailto:katherine.cox-buday@canonical.com" target="_blank">katherine.cox-buday@canonical<wbr>.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Seems like a good thing to do would be to ensure the tech board doesn't have any objections and then put it to a vote since it's more a property of the team and not the codebase.<br> <br> I just want some consistency until a decision is made. E.g. "we will be trying out GitHub reviews for the next two weeks; all reviews should be done on there".<br> <br> --<br> Katherine<br> <br> Nate Finch <<a href="mailto:nate.finch@canonical.com" target="_blank">nate.finch@canonical.com</a>> writes:<br> <br> > Can we try reviews on github for a couple weeks? Seems like we'll<br> > never know if it's sufficient if we don't try it. And there's no setup<br> > cost, which is nice.<br> ><br> > On Tue, Sep 20, 2016 at 12:44 PM Katherine Cox-Buday<br> > <<a href="mailto:katherine.cox-buday@canonical.com" target="_blank">katherine.cox-buday@canonical<wbr>.com</a>> wrote:<br> ><br> > I see quite a few PRs that are being reviewed in GitHub and not<br> > ReviewBoard. I really don't care where we do them, but can we<br> > please pick a direction and move forward? And until then, can we<br> > stick to our previous decision and use RB? With people using both<br> > it's much more difficult to tell what's been reviewed and what<br> > hasn't.<br> ><br> > --<br> > Katherine<br> ><br> > Nate Finch <<a href="mailto:nate.finch@canonical.com" target="_blank">nate.finch@canonical.com</a>> writes:<br> ><br> > > In case you missed it, Github rolled out a new review process.<br> > It<br> > > basically works just like reviewboard does, where you start a<br> > review,<br> > > batch up comments, then post the review as a whole, so you don't<br> > just<br> > > write a bunch of disconnected comments (and get one email per<br> > review,<br> > > not per comment). The only features reviewboard has is the edge<br> > case<br> > > stuff that we rarely use: like using rbt to post a review from a<br> > > random diff that is not connected directly to a github PR. I<br> > think<br> > > that is easy enough to give up in order to get the benefit of<br> > not<br> > > needing an entirely separate system to handle reviews.<br> > ><br> > > I made a little test review on one PR here, and the UX was<br> > almost<br> > > exactly like working in reviewboard:<br> > > <a href="https://github.com/juju/juju/pull/6234" rel="noreferrer" target="_blank">https://github.com/juju/juju/p<wbr>ull/6234</a><br> > ><br> > > There may be important edge cases I'm missing, but I think it's<br> > worth<br> > > looking into.<br> > ><br> > > -Nate<br> <br> --<br> Juju-dev mailing list<br> <a href="mailto:Juju-dev@lists.ubuntu.com" target="_blank">Juju-dev@lists.ubuntu.com</a><br> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailm<wbr>an/listinfo/juju-dev</a><br> </blockquote></div> </div></div><br>--<br> Juju-dev mailing list<br> <a href="mailto:Juju-dev@lists.ubuntu.com" target="_blank">Juju-dev@lists.ubuntu.com</a><br> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/juju-dev" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailm<wbr>an/listinfo/juju-dev</a><br> <br></blockquote></div><br></div> </div></div></blockquote></div><br></div>