Hi Igniters, Feb 10 is the due date for submitting the next board report. I would like to submit it a bit earlier, by the end of the day on Feb 9.
Here is the first version of the report (at the end of the email). Should we add here something important? What do you think if it worths mentioning/requires board attention: schema first discussions? IEP-61? Extensions release? Anything related to the 3.0 development approach? Sincerely, Dmitriy Pavlov ## Description: The mission of Ignite is the creation and maintenance of software related to High-performance, integrated, and distributed In-Memory Database and Caching Platform providing in-memory data caching, partitioning, processing, and querying components. ## Issues: There are no issues requiring board attention ## Membership Data: Apache Ignite was founded 2015-08-19 (5 years ago) There are currently 56 committers and 35 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - Alex Plehanov was added to the PMC on 2020-11-18 - Ivan Bessonov was added as a committer on 2021-01-19 - Nikita Amelchev was added as a committer on 2021-01-21 ## Project Activity: Development - Apache Ignite community voted to remove MVCC public API. Test and test suites on the TeamCity are under discussion. - 3.0.0-alpha1 was released on 2021-01-11, this release is the very first build made from standalone branch Ignite 3.0, such releases should help in early adoption and testing of 3.0 - 2.9.1 was released on 2020-12-28 (latest stable) - this release patches 2.9.0 and mostly contains fixes - 2.10.0 release is being prepared Events and conferences - Community members and Ignite users continue to run talks at online meetups ## Community Health: - dev@, user@ list traffic, and code contributions are almost the same as in the past quarter - Issues, PRs related activity have increased (from +14% to +49%)
