<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 2, 2018 at 8:27 PM, Shyamsundar Ranganathan <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@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><div style="font-family:"times new roman","new york",times,serif;font-size:12pt;color:rgb(0,0,0)"><div><h2 class="gmail-m_-4253946865992919278part" id="gmail-m_-4253946865992919278Meeting-date-05022018-May-02nd-2018-1930-IST-1400-UTC-1000-EDT">Meeting date: 05/02/2018 (May 02nd, 2018), 19:30 IST, 14:00 UTC, 10:00 EDT</h2><h3 class="gmail-m_-4253946865992919278part" id="gmail-m_-4253946865992919278BJ-Link">BJ Link</h3><ul class="gmail-m_-4253946865992919278part"><li>Bridge: <a href="https://bluejeans.com/205933580" target="_blank">https://bluejeans.com/<wbr>205933580</a><br></li><li>Download: <TBD><br></li></ul><h3 class="gmail-m_-4253946865992919278part" id="gmail-m_-4253946865992919278Attendance"></h3></div></div></div></blockquote><div>Download: <a href="https://bluejeans.com/s/fPavr">https://bluejeans.com/s/fPavr</a></div><div> </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div style="font-family:"times new roman","new york",times,serif;font-size:12pt;color:rgb(0,0,0)"><div><h3 class="gmail-m_-4253946865992919278part" id="gmail-m_-4253946865992919278Attendance">Attendance</h3><ul class="gmail-m_-4253946865992919278part"><li>Raghavendra M (Raghavendra Bhat), Kaleb, Atin, Amar, Nithya, Rafi, Shyam</li></ul><h3 class="gmail-m_-4253946865992919278part" id="gmail-m_-4253946865992919278Agenda">Agenda</h3><ul class="gmail-m_-4253946865992919278part"><li><p style="margin:0px">Commitment (GPLv2 Cure)</p><ul><li><a href="http://lists.gluster.org/pipermail/gluster-devel/2018-April/054751.html" target="_blank">Email</a> and <a href="https://review.gluster.org/19902" target="_blank">Patch</a><br></li><li>[amarts] 20+ people already have done +1. Will wait another 15days before any action on this.</li><li>AI: Send a reminder to the lists and get the changes merged around next maintainers meeting [Amar]</li></ul></li><li><p style="margin:0px">GD2 testing upstream</p><ul><li>Is there a glusterd v1 Vs v2 parity check matrix?<ul><li>Functional parity of the CLI</li></ul></li><li>As the cli format is not 100% compatible, how to proceed further with regression tests without much fuss?<ul><li>[amarts] Easier option is to handle it similar to brick-mux test. Create a new directory ‘tests2/’ which is copy of current tests, and files changed as per glusterd2/glustercli needs. We can do bulk replace etc etc… start small, make incremental progress. Run it once a day.<ul><li>Add smoke check for core glusterfs to keep things working with GD2</li><li>Add GD2 tests into the said patch, to ensure functionality of GD2 itself</li><li>Approach ack: Shyam</li><li>Approach nack:</li></ul></li></ul></li></ul></li><li><p style="margin:0px">Coding standards</p><ul><li>Did we come to conclusion? What next?<ul><li>Need some more votes to take it forward</li><li>Settle current conflicts to the settings</li></ul></li><li>[amarts] Need to see what should be ‘deadline’ for this. Ideal to have before 4.1, or else backporting would be serious problem.</li><li>AI: Reminder mail on release to get this closed [Shyam]</li><li>Conversion work should be doable in 1/2 a day</li><li>Per-patch format auto-verifier/correction job readiness<ul><li>Possibly not ready during roll-out</li><li>Not looking at it as the blocker, as we can get it within a week and sanitize patches that were merged in that week [Shyam]</li></ul></li></ul></li><li><p style="margin:0px">Branching for 4.1?</p><ul><li>Today would be branching date [Shyam]<ul><li>No time to fold slipping features, as we are 2 weeks off already!</li><li>Branching is on 4th May, 2018, what makes it gets in, rest is pushed to 4.2</li></ul></li><li>Leases?</li><li>Ctime?</li><li>Thin-Arbiter?</li><li><Any other features>?</li></ul></li><li><p style="margin:0px">Round Robin:</p><ul><li>[amarts] - Is the plan for version change (or not change) ready after 4.1? or do we need to extend the period for this?<ul><li>AI: Send proposal to devel -> users and take action on getting this done before 4.2</li><li>Fold in xlator maturity states into the same release</li></ul></li><li>[kkeithley] - new (untriaged) upstream bugs list is getting longer.<ul><li>Triage beyond assignment</li><li>Tracking fixes and closure of the same</li><li>AI: Shyam to work on this and next steps</li></ul></li></ul></li></ul><h3 class="gmail-m_-4253946865992919278part" id="gmail-m_-4253946865992919278Decisions-and-Actions">Decisions and Actions</h3><ul class="gmail-m_-4253946865992919278part"><li>AI (GPL cure): Send a reminder to the lists and get the changes merged around next maintainers meeting [Amar]</li><li>Decision: GD2 tests to create a patch of tests and work on it using nightly runs to get GD2 integrated</li><li>AI (format conversion): Reminder mail on release to get this closed [Shyam]</li><li>AI (format conversion): Conversion done Thursday, ready for merge Friday [Amar/Nigel]</li><li>Decision (4.1 branching): 4.1 branching date set at 4th May, no feature slips allowed beyond that [Shyam]</li><li>AI (release cadence and version numbers change): Send proposal to devel -> users and take action on getting this done before 4.2 [Shyam]</li><li>AI (Bugs triage cadence): Shyam to work on this and next steps [Shyam]</li></ul></div></div></div><br>______________________________<wbr>_________________<br>
maintainers mailing list<br>
<a href="mailto:maintainers@gluster.org">maintainers@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/maintainers" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/maintainers</a><br>
<br></blockquote></div><br><br clear="all"><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></div>