Hi! I reviewed our activity in PR/dev e-mail list and Community meeting reports. Here is the report I created:
*How has the community developed since the last report*? - Mailing list Activity: 82 new emails on the Dev mailing list since the last report, covering community, repositories, support, technical and Apache-related discussions. - GitHub Discussions: 5 new threads since last report. New Committers: Rose Duan [email protected] roseduan HashData Events: - Apache Cloudberry Meetup organized in Shenzhen: 30+ attendees on Jan 17th - Commenced Apache Cloudberry Bi-weekly Community Meeting, see details in https://docs.google.com/document/d/14NLYVvApvijsQDt7uCKblVPKhayJSxb6na9dMAp5NAM/edit?tab=t.0, The 1st meeting was held on January 30, 2026. *How has the project developed since the last report*? - cloudberry-pxf. After several months of continuous effort, the PXF project has recently achieved a significant milestone: 1. The code baseline has been 100% aligned with the archived pxf-archive from GP. 2. Completed full adaptation for Cloudberry. 3. Added a relatively comprehensive and extensive CI pipeline for PXF. - PostgreSQL Kernel upgrade (14~>16): the work has been in progress. The latest status: ~> Merge New Kernel into Work Branch (Done) ~> Resolve Conflicts (Done) ~> Fix Compile Errors (Done) ~> Init Database (Done) ~> Start the cluster (Done) ~> Pass the Postgres parallel schedule tests (Done) ～> Pass the Cloudberry schedule tests (Will start) At this stage, most of the core enablement work for PostgreSQL 16.9 has been completed. Next, we will start to try to pass the Cloudberry schedule tests. - Performance PAX: optimize io read for multiple discrete columns in a group Add UDP2 interconnect protocol implementation (right now is still experimental feature) Set join_collapse_limit default value to 13 - Stability 1. Merge 72 commits, most of them - bugfixes and CI/CD improvements 2. Fix 2 CVE`s 3. Merge 244 commits to REL_2_STABLE. We're ready to release cloudberry 2.1. - Ecosystem 1. Added support Ubuntu 22.04 and debian packages to CI/CD 2. Added support Rocky Linux 8 to CI/CD 3. Squash cloudberry-bootcamp repository into devops/sandbox main repository catalog 4. Madlib integration is still under the progress. We successfully performed manual tests, but PR is still open https://github.com/apache/madlib/pull/627 3. Working on diskquota extension integration still in progress - see https://github.com/apache/cloudberry/pull/1490 *When were the last committers or PPMC members elected*? Rose Duan, 19th Jan 2026 On Mon, Feb 2, 2026 at 6:13 PM Leonid Borchuk <[email protected]> wrote: > Hi! > > I found out the November report > https://cwiki.apache.org/confluence/display/INCUBATOR/November2025 > > Am I understanding correctly that we can leave all the questions as in the > old report and only fill in those that reflect actual activity? - > > How has the community developed since the last report? > <https://cwiki.apache.org/confluence/display/INCUBATOR/November2025#how-has-the-community-developed-since-the-last-report-1>How > has the project developed since the last report? > <https://cwiki.apache.org/confluence/display/INCUBATOR/November2025#how-has-the-project-developed-since-the-last-report-1> > When were the last committers or PPMC members elected? > <https://cwiki.apache.org/confluence/display/INCUBATOR/November2025#when-were-the-last-committers-or-ppmc-members-elected-1> > > On Mon, Jan 26, 2026 at 5:38 AM Dianjin Wang <[email protected]> > wrote: > >> Hi all, >> >> Would any PPMC members or committers like to take responsibility for >> drafting the report this time? This way, more PPMC members or >> committers can become familiar with the process. I'm happy to help. >> >> Best, >> Dianjin Wang >> >> On Mon, Jan 26, 2026 at 6:19 AM <[email protected]> wrote: >> > >> > Dear podling, >> > >> > This email was sent by an automated system on behalf of the Apache >> > Incubator PMC. It is an initial reminder to give you plenty of time to >> > prepare your quarterly board report. >> > >> > The board meeting is scheduled for Wed, 18 February 2026. >> > The report for your podling will form a part of the Incubator PMC >> > report. The Incubator PMC requires your report to be submitted 2 weeks >> > before the board meeting, to allow sufficient time for review and >> > submission (Wed, February 04). >> > >> > Please submit your report with sufficient time to allow the Incubator >> > PMC, and subsequently board members to review and digest. Again, the >> > very latest you should submit your report is 2 weeks prior to the board >> > meeting. >> > >> > Candidate names should not be made public before people are actually >> > elected, so please do not include the names of potential committers or >> > PPMC members in your report. >> > >> > Thanks, >> > >> > The Apache Incubator PMC >> > >> > Submitting your Report >> > >> > ---------------------- >> > >> > Your report should contain the following: >> > >> > * Your project name >> > * A brief description of your project, which assumes no knowledge of >> > the project or necessarily of its field >> > * A list of the three most important issues to address in the move >> > towards graduation. >> > * Any issues that the Incubator PMC or ASF Board might wish/need to be >> > aware of >> > * How has the community developed since the last report >> > * How has the project developed since the last report. >> > * How does the podling rate their own maturity. >> > >> > This should be appended to the Incubator Wiki page at: >> > >> > https://cwiki.apache.org/confluence/display/INCUBATOR/February2026 >> > >> > Note: This is manually populated. You may need to wait a little before >> > this page is created from a template. >> > >> > Note: The format of the report has changed to use markdown. >> > >> > Mentors >> > ------- >> > >> > Mentors should review reports for their project(s) and sign them off on >> > the Incubator wiki page. Signing off reports shows that you are >> > following the project - projects that are not signed may raise alarms >> > for the Incubator PMC. >> > >> > Incubator PMC >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
