The Accumulo community decided to draft the Apache community reports on the Accumulo dev list – and this is a draft of the January report for review / comments. The report is due by Wednesday, January 8th.
The following is cut-n-paste directly from the tool - formatting differences should not be reflected in the tool submission. Ed Coleman --- report text from reporter tool --- ## Description: The mission of Apache Accumulo is the creation and maintenance of software related to a robust, scalable, distributed key/value store with cell-based access control and customizable server-side processing. ## Project Status: Current project status: Ongoing with high activity. Issues for the board: None ## Membership Data: Apache Accumulo was founded 2012-03-20 (13 years ago) There are currently 43 committers and 39 PMC members in this project. The Committer-to-PMC ratio is roughly 6:5. Community changes, past quarter: - No new PMC members. Last addition was Kevin Rathbun on 2024-07-24. - No new committers. Last addition was Kevin Rathbun on 2024-07-25. ## Project Activity: ### Releases: - accumulo-1.10.4 (legacy) was released on 2023-11-16. - accumulo-2.1.3 (LTM) was released on 2024-08-12. - accumulo-3.0.0 was released on 2023-08-21. - accumulo-access-1.0.0-beta was released on 2024-02-17. ### Planned Release Activity: Accumulo is currently working on some significant development efforts. With the release of 2.1.3, we have begun formalizing future release plans: - Continue with critical bug fixes of the 2.1.x line. - Work continues on 3.1 branch to prepare for a feature-freeze and a release preparation. No target date has been set. - We continue to work towards a 4.0.0-alpha release. These changes are the evolution of the processing model to support dynamic scaling and provide elasticity for improved cost and performance management. These changes are outlined in [1] ### Notable Work: - Metrics improvements - Monitor rework to support new processing model - Stability and scaling improvements to support elasticity ## Community Health: Overall community health is good and GitHub activity remains consistent. The email traffic reflects the community preference of using GitHub projects and issues for PRs discussions. We also use our slack channel for day-to-day communications. We continue to use the mailing list for official Apache business and it remains a channel for users to contact us. ## Links: [1] https://accumulo.apache.org/blog/2024/10/07/accumulo4-preview.html --- end text
