LGTM On Mon, Jul 8, 2024 at 5:19 PM Dominic Garguilo <domgargu...@apache.org> wrote:
> Looks good! Thanks! > > On Mon, Jul 8, 2024 at 5:13 PM Daniel Roberts <ddani...@gmail.com> wrote: > > > > Minor update to the "Other" section: > > --- > > During the past quarter, Accumulo had an opportunity to perform at-scale > > testing of 2.1 experimental features, namely ScanServers and External > > Compactors. > > This testing period did uncover an important performance issue with > > ScanServers > > that has now been resolved in the 2.1.3 version. > > The at-scale testing also exposed the need for additional metric and > > logging changes. > > At present, most of these minor issues have been resolved and > > incorporated into 2.1.3 and future release branches. Overall, the testing > > successfully validated scalability and performance improvements and > > demonstrated the stability of new Accumulo features at scale. > > --- > > > > Overall it looks good! > > > > On Sun, Jul 7, 2024 at 9:49 PM Ed Coleman <edcole...@apache.org> wrote: > > > > > The Accumulo community decided to draft the Apache community reports > on the > > > Accumulo dev list – and this is a draft of the April report for review > / > > > comments. The report is due by Wednesday, July 10th. The text below is > > > copied from the reporting tool and may not reflect the final > formatting of > > > the final report when submitted. > > > > > > Ed Coleman --- begin report text from report 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 (12 years ago) There are > currently > > > 42 > > > committers and 39 PMC members in this project. The Committer-to-PMC > ratio > > > is > > > roughly 1:1. It is our practice to invite committers to be PMC members > at > > > the > > > same time. The difference between committers and PMC members is because > > > some > > > PMC members have elected to go emeritus. > > > > > > Community changes, past quarter: > > > - No new PMC members. Last addition was Daniel Roberts on 2023-08-08. > > > - No new committers. Last addition was Daniel Roberts on 2023-08-10. > > > > > > ## Project Activity: > > > > > > Accumulo is currently working on some significant development efforts. > > > - Improving the performance and stability of the 2.1.x line > > > - Adding new features and performance improvements to 3.1 line > > > - The evolution of the processing model to support dynamic scaling and > > > provide > > > elasticity. > > > > > > ### Releases: > > > - accumulo-1.10.4 was released on 2023-11-16. > > > - accumulo-2.1.2 was released on 2023-08-21. > > > - accumulo-3.0.0 was released on 2023-08-21. > > > - accumulo-access-1.0.0-beta was released on 2024-02-17. > > > > > > The Accumulo 1-10.x line reached end-of-life and Accumulo-1.10.4 is the > > > final > > > release. The vote thread can be found at [1] > > > > > > Release activity for a 2.1.3 release has started. A pre-release RC-0 > vote > > > started on 2 July 2024. (The pre-release vote is to validate the > release > > > process before formal releases are created.) > > > > > > Work on 3.1.0 and future elasticity branches remain very active. > > > > > > ### Other: > > > > > > During the past quarter, Accumulo had an opportunity to perform > at-scale > > > testing. There were a number of minor issues that were resolved and > > > incorporated into 2.1.3 and future release branches. Overall, the > testing > > > successfully validated scalability and performance improvements and > > > demonstrated the stability of new Accumulo features at scale. > > > > > > ## 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 planning and PRs for code discussions. We also use our slack > > > channel for day-to-day communications. We continue to use the mailing > list > > > for > > > official Apache business and remains a channel for users to contact us. > > > > > > ## Links > > > [1] https://lists.apache.org/thread/6jy0v0qk14163xx19ocz4l3xxc1rzr3z > > > [2] https://lists.apache.org/thread/5tlykw1o5rcz5vps5gz4vo1o7kjnpsld > > > >
