<div dir="ltr">HI Darragh,<div><br></div><div>I would like to help where I can in the reviews, but Tuesdays and Thursdays are my busiest days. I can only guarantee that I am free after 19:00 UTC on Tuesdays and Thursdays. Monday and Fridays are days where I am free from summer class obligations but I am not too sure if that will work with everyone else.</div><div><br></div><div>Regards,</div><div>Kien Ha</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 4, 2016 at 8:47 PM, Dong Ma <span dir="ltr"><<a href="mailto:winterma.dong@gmail.com" target="_blank">winterma.dong@gmail.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><p class="MsoNormal" align="left"><span lang="EN-US" style="font-size:12pt;font-family:Consolas">Hey Darragh,</span></p><p class="MsoNormal" align="left"><span lang="EN-US" style="font-size:12pt;font-family:Consolas"> </span></p><p class="MsoNormal" align="left"><span lang="EN-US" style="font-size:12pt;font-family:Consolas">I agree with your thought and would like
to participate to the reviews, although the time slots is a little late for me
but it works.</span></p><p class="MsoNormal" align="left"><span lang="EN-US" style="font-size:12pt;font-family:Consolas"> </span></p><p class="MsoNormal" align="left"><span lang="EN-US" style="font-size:12pt;font-family:Consolas">Thanks,</span></p><p class="MsoNormal" align="left"><span lang="EN-US" style="font-size:12pt;font-family:Consolas">Dong Ma (Vincent)</span></p><p class="MsoNormal" align="left"><span lang="EN-US" style="font-size:12pt;font-family:Consolas"> </span></p><p class="MsoNormal" align="left"><span lang="EN-US" style="font-size:12pt;font-family:Consolas">Email: <a href="mailto:winterma.dong@gmail.com" target="_blank">winterma.dong@gmail.com</a></span></p><p class="MsoNormal" align="left"><span lang="EN-US" style="font-size:12pt;font-family:Consolas">IRC: larainema</span></p><p class="MsoNormal" align="left"><span lang="EN-US" style="font-family:Consolas">
</span></p><p class="MsoNormal" align="left"><span lang="EN-US" style="font-size:12pt;font-family:Consolas">Telephone: <a href="tel:%2B86%2018610023880" value="+8618610023880" target="_blank">+86 18610023880</a></span></p></div><div><br><div><br></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">2016-07-05 0:43 GMT+08:00 Darragh Bailey <span dir="ltr"><<a href="mailto:daragh.bailey@gmail.com" target="_blank">daragh.bailey@gmail.com</a>></span>:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div><div><div>Hi,<br><br><br></div><div>To try and minimise trashing of both core reviews and V2.0 patch author(s), I'd like to propose that we pick a time/day every second week for 3-4 iterations where those interested set aside a set block of time to collaborate in getting the main rework patches landed. Consider it a set of mini bug days focused on JJB 2.0 API changes.<br><br></div><div>To get the ball rolling, I'm going to suggest one of the following 2 timezones (obviously these suit me best, but I'm available the other days as well):<br></div><div>14:00-1800 UTC Thurs (Staring 7th July - not available the 14th hence suggesting this Thurs)<br>14:00-1800 UTC Tues (Staring 12th July)<br></div><div><br></div><div>I'm assuming that later in the day for me aligns better with others, but I could be very wrong.<br></div><div><br></div><div>Also thinking that spinning up a temporary public dedicated IRC chat room would be helpful here, probably look to avoid using one of the existing meeting rooms because I'm assuming that would conflict with other teams, unless someone tells me there is a simple solution to this. Only negative I can see is that the chats wouldn't be logged.<br><br><br></div><div><br></div><div>More info below on why suggest this:<br></div><div><br><br></div>Having gone through a few cycles where patches get reviewed, reworked and then broken by other changes landing, reworked again, reviewed and broken again, it can be quite onerous on both author and reviewer getting a change that touches a number of places to land as the risk of another patch landing causing a merge failure increases dramatically the more places the patch touches.<br><br></div><div>The set of V2 patches has to bring the existing code through some amount of interim steps to make it easy to review, unfortunately given the amount of rework to do, the odds of anything else triggering a conflict is pretty high and basically faced with the following choices:<br><ul><li>Take a long time complete the cycle of rework -> review -> rework -> break -> rework ->. ...</li><li>Block landing any changes that touch any of the code impacted by V2 work until most V2 patches are landed.<br></li></ul></div><div></div><div><br><br></div>However we can get enough cores on around the same time and try for some synchronized collaboration, I think it's probably far easier to land a series of patches over a few meetings and get everything far enough along with much less workload placed on everyone involved that we can then revert back to the more async approach without the same issues around the remaining changes.<br></div><div><br></div>Expect that this would only take 3-4 of these to get the major part of the rewrite in place.<br><div><div><div><div><br></div><div>Thoughts? Does this work for enough other JJB reviewers?<span><font color="#888888"><br><br clear="all"><div><br>-- <br><div data-smartmail="gmail_signature">Darragh Bailey<br>"Nothing is foolproof to a sufficiently talented fool"</div>
</div></font></span></div></div></div></div></div>
<br></div></div>_______________________________________________<br>
OpenStack-Infra mailing list<br>
<a href="mailto:OpenStack-Infra@lists.openstack.org" target="_blank">OpenStack-Infra@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
OpenStack-Infra mailing list<br>
<a href="mailto:OpenStack-Infra@lists.openstack.org">OpenStack-Infra@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra</a><br>
<br></blockquote></div><br></div>