Hi everyone, For a first time, things went amazingly smooth with Zoom and having a good exchange and participation.
Scott already provided the link but I'll just offer up a quick summary from the meeting notes and an easy reminder for those that volunteered for something. All notes and link to recorded video can be found here: https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+Contributor+Meeting *Meeting Notes:* The community and contributors remain focussed on the 4.0 release. There was broad consensus that we want to keep working towards the 4.0 QA Test Plan <https://cwiki.apache.org/confluence/display/CASSANDRA/4.0+Quality%3A+Components+and+Test+Plans> and a call for contributors to sign up for major components. We also touched on a number of other process discussions and agreed to take a few discussions to the mailing list. Action Items: - *All contributors:* please sign up as either shepherds or contributors on the test plan. If we want 4.0 to happen we must get at least minimal coverage of these areas. - Ahead of next call, review open tickets with “patch available” for Alpha and seek reviewers; for unassigned tickets, seek assignees or open discussion on scope. - Discuss on dev list: - Thread regarding when to branch for a post-4.0 release. - Cadence of meeting: Consensus on call was “once a month, at an earlier time to enable more from European time zones to join - likely rotating.” - Windows question: potentially a question to the user@ list if there are contributors willing to test / contribute patches for Windows. - Jeremy Hanna: Discuss changes to defaults prior to 4.0 release. - Patrick McFadin: Start discussion on dev list to settle time for next meetings and frequency. - Anthony raising need for Reaper compatibility testing to other Reaper contributors; will note compatibility issues identified (in case they warrant a change in C* itself). - Josh preparing JIRA epics that capture current headings in the Confluence “4.0 open issues” report. I will start a separate thread about the time and frequency. Any general feedback/suggestions about the logistics of the meeting can be done in this thread. Patrick
