<div dir="ltr"><h3 class="gmail-part" id="gmail-bj-link" style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";line-height:1.25;color:rgb(51,51,51);margin-top:24px;margin-bottom:16px;font-size:1.25em;letter-spacing:0.35px">BJ Link</h3><ul class="gmail-part" style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em;color:rgb(51,51,51);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;letter-spacing:0.35px"><li class="gmail-" style="box-sizing:border-box">Bridge: <a href="https://bluejeans.com/205933580" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">https://bluejeans.com/205933580</a></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Download: <a href="https://bluejeans.com/s/eFJy" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">https://bluejeans.com/s/eFJy</a></li></ul><h3 class="gmail-part" id="gmail-attendance" style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";line-height:1.25;color:rgb(51,51,51);margin-top:24px;margin-bottom:16px;font-size:1.25em;letter-spacing:0.35px"><a class="gmail-anchor gmail-hidden-xs" href="https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQCMCYIQA===?both#attendance" title="attendance" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1"><span class="gmail-octicon gmail-octicon-link" style="box-sizing:border-box;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a>Attendance</h3><ul class="gmail-part" style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em;color:rgb(51,51,51);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;letter-spacing:0.35px"><li class="gmail-" style="box-sizing:border-box">[Sorry Note] misc, Atin (Conflicting meeting), Csaba</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Amar, Nigel, Nithya, Xavi, Ravi, Mohit Agrawal, Shyam, Deepshika, Kaushal, Niels (late, BlueJeans–)</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><Add your name here></li></ul><h3 class="gmail-part" id="gmail-agenda" style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";line-height:1.25;color:rgb(51,51,51);margin-top:24px;margin-bottom:16px;font-size:1.25em;letter-spacing:0.35px"><a class="gmail-anchor gmail-hidden-xs" href="https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQCMCYIQA===?both#agenda" title="agenda" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1"><span class="gmail-octicon gmail-octicon-link" style="box-sizing:border-box;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a>Agenda</h3><ul class="gmail-part" style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em;color:rgb(51,51,51);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;letter-spacing:0.35px"><li class="gmail-" style="box-sizing:border-box"><p style="box-sizing:border-box;margin:16px 0px">Action items from last meeting:</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[nigelb] Metrics on first-time contributors?</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">[nigelb] Cregit run?<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Both to be tracked as bugzilla bug, request queue full atm.</li></ul></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Re-visiting closing old reviews [nigelb]</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Using Gerrit to do the initial closing is a bad idea.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">We have a lot of reviews and each abandon triggers an email to everyone involved.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">This means Gerrit server will get greylisted by all providers as we did for stage recently.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">We have a Jenkins job that will close a few old reviews every day. Currently thinking of 25 per day. Once we catch up, we can either continue with the bot or use Gerrit to do this.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Is the plan sounding fine?<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Yes</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Review: <a href="https://review.gluster.org/#/c/18734/" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">https://review.gluster.org/#/c/18734/</a></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Release sanity [nigelb]</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">We run regression-test-burn-in for master.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">We don’t for release branches. Seems like a no-brainer to do this.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">However, this will add load onto regression machines 1x number of active releases per day.<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">This occupies machines, should we run such things once daily, so that we can keep regression machines free?<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Are we not moving towards reducing regression time, so this is not a problem?</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Need more regression machines to pull this off</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Move the job to Eastern TZ (mid-day or later) as that is a relatively free of regression jobs zone.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">More patches in one job, means finding out what caused failure would be more difficult<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">This possibly can be handled using git bisect and other such.</li></ul></li></ul></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Options to mitigate<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">We will trigger a regression run only if there are changes since last run.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Shall we move regression-test-burn-in to nightly?</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">We (release-owners) need the ability to trigger this job, so that a release can be made (releatively) deterministically [Shyam]</li></ul></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Jeff’s email on Pressing ‘Submit’ if everything is OK?</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">What is stopping you from doing it?<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Assumption is that maintainer of the component merges the patch</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Not focussing on the patch backlog due to other constraints</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Xavi is taking good initiative here, need more of the same</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">We need a catch all case when patches are not moving, than depend/rely on maintainers always<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Master dashboard: <a href="https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:master-dashboard" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">https://review.gluster.org/#/projects/glusterfs,dashboards/dashboard:master-dashboard</a></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Components in the fringe are often ignored, and need attention (for example hooks or such)</li></ul></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Regression Suggestion:</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Should author wait for at least one sanity review before running regression?<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Current regression takes time, so not running on local machines</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Sometimes reviewers see patches only post a regression score</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">People trigger regression before smoke finishes, which is bad! (when smoke fails)<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Should we pipeline this, regression only if smoke passes. This may lead to some trouble with voting, needs a bit of expperimentation.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">This could be a problem in terms of people running random code on our tests.</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Release branches is better to get regression votes before review, as release-owners may need to review and merge in the window that they work with the branch/release [Shyam]</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Decision: Not yet! (wait for regression jobs to run faster)</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Will save some cycles as I have seen authors doing ‘+1’ to verify immediately, and then they get -1.</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Makes sense if their patch gets reviewed just after smoke (or even without smoke +1 too)<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Atin] I have a disagreement of author to wait for review before marking the patch verified +1. To me, it’s author’s responsibility to ensure the basic regression is passed and that way maintainers get a confidence on the sanity of the patch. As a GlusterD & CLI maintainer, most of the times I look at reviewing patches (in 90 - 95% cases) which have passed regression.</li></ul></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">‘experimental’ branch rebase</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Major conflicts with posix changes :-/<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Shyam to blame :/</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">AI: Shyam to sync with Amar and get this moving (Shyam)</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Other option changes which GD2 was dependent on, is sent to master with <code style="box-sizing:border-box;font-family:Menlo,Monaco,Consolas,"Courier New",monospace;font-size:13.6px;padding:0.2em 0px;background-color:rgba(0,0,0,0.04);border-radius:3px;margin:0px;color:inherit">--author</code> set to original authors.</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">4.0 Schedule [Shyam]</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">Slated for branching mid Dec, are we ready?<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">GD2 still a lot to be done</li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Do we have burn down charts?<ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">AI: Do this weekly (Shyam)</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">Example: <a href="http://radekstepan.com/burnchart/#!/gluster/glusterfs/3" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">http://radekstepan.com/burnchart/#!/gluster/glusterfs/3</a></li></ul></li></ul></li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em"><p style="box-sizing:border-box;margin:16px 0px">Round Table:</p><ul style="box-sizing:border-box;margin-top:0px;margin-bottom:0px;padding-left:2em"><li class="gmail-" style="box-sizing:border-box">[Ravi] Patch <a href="https://review.gluster.org/#/c/17673/" target="_blank" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none">https://review.gluster.org/#/c/17673/</a> for 3.13 is acceptable? </li><ul><li class="gmail-" style="box-sizing:border-box">AI: Shyam to get back on this (by Nov-16-2017)</li></ul></ul></li></ul><h3 class="gmail-part" id="gmail-decisions" style="box-sizing:border-box;font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";line-height:1.25;color:rgb(51,51,51);margin-top:24px;margin-bottom:16px;font-size:1.25em;letter-spacing:0.35px"><a class="gmail-anchor gmail-hidden-xs" href="https://hackmd.io/MYTgzADARgplCGBaA7DArMxAWAZvATIiFhJgCYarBQCMCYIQA===?both#decisions" title="decisions" style="box-sizing:border-box;background-color:transparent;color:rgb(51,122,183);text-decoration-line:none;float:left;padding-right:4px;line-height:1"><span class="gmail-octicon gmail-octicon-link" style="box-sizing:border-box;font-weight:normal;font-stretch:normal;font-size:16px;line-height:1;font-family:octicons;display:inline-block;color:rgb(0,0,0);vertical-align:middle"></span></a>Decisions</h3><ul class="gmail-part" style="box-sizing:border-box;margin-top:0px;margin-bottom:16px;padding-left:2em;color:rgb(51,51,51);font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Roboto,"Helvetica Neue",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI Emoji","Segoe UI Symbol";font-size:16px;letter-spacing:0.35px"><li class="gmail-" style="box-sizing:border-box">Jenkins job to retire older reviews: Ack to do this, in batches</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">regression-test-burn-in for release branches: Ack</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">regression-test-burn-in on demand for release branches: (I think this was an Ack from Infra folks)</li><li class="gmail-" style="box-sizing:border-box;margin-top:0.25em">regression-test-burn-in for master moved to nightly (close to mid-day easter TZ): Ack</li></ul><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>
</div>