The Apache Software Foundation Board of Directors Meeting Minutes May 20, 2026 1. Call to order The meeting was scheduled for 21:00 UTC and began at 21:02 when a sufficient attendance to constitute a quorum was recognized by the chair. Other Time Zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=2026-05-20T21:00:00&msg=ASF+Board+Meeting The meeting was held via teleconference, hosted by the Secretary via Zoom. The #asfboard channel on the-asf.slack.com was used for backup. 2. Roll Call Directors Present: Zili Chen Shane Curcuru Christofer Dutz Emmanuel Lécharny Justin Mclean Jean-Baptiste Onofré Christopher Schultz Greg Stein Sander Striker Directors Absent: none Executive Officers Present: Craig McClanahan Ruth Suehle Craig L Russell Daniel Ruggeri Executive Officers Absent: Matt Sicker Guests: Daniel Gruno Alin Jerpelea Paul King Piotr Karwasz Jan Friedrich Mark J. Cox Thomas Neidhart Daniel Sahlberg Jarek Potiuk Brian Proffitt Paul Irwin Henri Yandell Whitney P True Dave Fisher 3. Minutes from previous meetings Published minutes can be found at: https://www.apache.org/foundation/board/calendar.html A. The meeting of April 15, 2026 See: board_minutes_2026_04_15.txt Approved by General Consent. B. The meeting of March 18, 2026 See: board_minutes_2026_03_18.txt Tabled. 4. Executive Officer Reports A. Board Chair [Sander Striker] We have a light agenda this month; there are numerous internal discussions but no proposals for the board to discuss this month. B. President [Ruth Suehle] D&O insurance in process of being renewed. We received a small bill from the PA department of labor for unemployment compensation tax from 2020/21 that hadn't been paid. This has now been paid. I'll be keynoting Berlin Buzzwords in a few weeks--hope to see ASF folks there. Additionally, please see Attachments 1 through 11. C. Treasurer [Craig McClanahan] Normal operations continue, particularly including preparatory work for our audit that is about to commence. Final month-end financial reports were posted to board@ as usual. The size of the Anthropic contribution caused a couple of unusual ripples worth noting: * The $1.5m was invoiced in March, so it was recorded there as a one-time contribution in that month. * Payment was received in April, which caused our cash balance to increase. This raises an accounting-related question related to the Responsible AI Initiative: do we intend to track specific expenditures against that to Responsible AI Initiative accounts? If so, we should get those established soon. D. Secretary [Matt Sicker] In April, the Secretary recorded 53 ICLAs, one Membership Application, two Software Grants, and two Corporate Contributor License Agreements. E. Executive Vice President [Daniel Ruggeri] Little to report. Geared up and actively watching the flow of comms. Setting up discussion with Ruth and a 2nd degree connection regarding a legal question. F. Vice Chair [Justin Mclean] Nothing to report. Executive officer reports approved as submitted by General Consent. 5. Additional Officer Reports A. VP of W3C Relations [Andy Seaborne / Sander Striker] See Attachment 12 B. Apache Legal Affairs Committee [Roman Shaposhnik / Justin Mclean] See Attachment 13 C. Apache Security Team Project [Mark J. Cox / Shane Curcuru] See Attachment 14 Additional officer reports approved as submitted by General Consent. 6. Committee Reports Summary of Reports The following reports required further discussion: # BVal [elecharny] # BuildStream [elecharny] # Geode [cdutz] # HTTP Server [jmclean] # Hop [jmclean] # Impala [jmclean] # Kylin [elecharny, schultz, jmclean] # Legal Affairs [jmclean] # Ozone [jmclean] # Perl [jmclean] # Spark [jmclean] # Superset [jmclean] # Xalan [elecharny] A. Apache AGE Project [Jeff Jirsa / Greg Stein] No report was submitted. B. Apache Airavata Project [Suresh Marru / Emmanuel Lécharny] See Attachment B C. Apache Ambari Project [Brahma Reddy Battula / Christofer Dutz] See Attachment C D. Apache Ant Project [J Pai / Zili Chen] No report was submitted. E. Apache Artemis Project [Christopher L. Shannon / Jean-Baptiste Onofré] See Attachment E F. Apache Avro Project [Ryan Skraba / Christopher Schultz] See Attachment F G. Apache BookKeeper Project [Enrico Olivelli / Christofer Dutz] See Attachment G H. Apache Brooklyn Project [Juan D. Cabrerizo / Justin Mclean] See Attachment H I. Apache BuildStream Project [Abderrahim Kitouni / Emmanuel Lécharny] See Attachment I J. Apache BVal Project [Matt Benson / Shane Curcuru] See Attachment J @Shane Curcuru: roll call for BVAL K. Apache Cassandra Project [Ekaterina Dimitrova / Greg Stein] See Attachment K L. Apache Celeborn Project [Keyong Zhou / Jean-Baptiste Onofré] See Attachment L M. Apache Community Development Project [Swapnil Mane / Christopher Schultz] See Attachment M N. Apache CouchDB Project [Jan Lehnardt / Zili Chen] No report was submitted. O. Apache Creadur Project [Philipp Ottlinger / Sander Striker] See Attachment O P. Apache DataFu Project [Eyal Allweil / Greg Stein] See Attachment P Q. Apache DataSketches Project [Lee Rhodes / Shane Curcuru] See Attachment Q R. Apache DeltaSpike Project [Mark Struberg / Justin Mclean] See Attachment R S. Apache Doris Project [Mingyu Chen / Emmanuel Lécharny] See Attachment S T. Apache Drill Project [Charles Givre / Sander Striker] No report was submitted. U. Apache Druid Project [Abhishek Agarwal / Jean-Baptiste Onofré] No report was submitted. V. Apache Empire-db Project [Rainer Döbele / Christopher Schultz] See Attachment V W. Apache EventMesh Project [Eason Chen / Zili Chen] See Attachment W X. Apache FreeMarker Project [Dániel Dékány / Christofer Dutz] See Attachment X Y. Apache Geode Project [Mark Bretl / Christofer Dutz] See Attachment Y Z. Apache Geronimo Project [Jean-Louis Monteiro / Greg Stein] No report was submitted. AA. Apache Gluten Project [Weiting Chen / Jean-Baptiste Onofré] See Attachment AA AB. Apache Grails Project [James Fredley / Emmanuel Lécharny] See Attachment AB AC. Apache Groovy Project [Paul King / Shane Curcuru] See Attachment AC AD. Apache Hop Project [Hans Van Akelyen / Justin Mclean] No report was submitted. @Justin Mclean: suggest chair change AE. Apache HTTP Server Project [Joe Orton / Sander Striker] See Attachment AE AF. Apache HttpComponents Project [Michael Osipov / Zili Chen] See Attachment AF AG. Apache Ignite Project [Dmitry Pavlov / Christopher Schultz] See Attachment AG AH. Apache Impala Project [Zoltán Borók-Nagy / Greg Stein] See Attachment AH @Justin Mclean: include the last release date in the report AI. Apache Incubator Project [Justin Mclean / Justin Mclean] See Attachment AI AJ. Apache Johnzon Project [Jean-Louis Monteiro / Jean-Baptiste Onofré] See Attachment AJ AK. Apache Juneau Project [James Bognar / Justin Mclean] See Attachment AK AL. Apache Kafka Project [Mickael Maison / Sander Striker] See Attachment AL AM. Apache Knox Project [Larry McCay / Emmanuel Lécharny] See Attachment AM AN. Apache Kylin Project [Yang Li / Christopher Schultz] See Attachment AN @Christopher Schultz: discuss failed roll call and future direction AO. Apache Libcloud Project [Tomaž Muraus / Christopher Schultz] See Attachment AO AP. Apache Logging Services Project [Piotr Karwasz / Shane Curcuru] See Attachment AP AQ. Apache Lucene.Net Project [Shad Storhaug / Emmanuel Lécharny] See Attachment AQ AR. Apache ManifoldCF Project [Piergiorgio Lucidi / Greg Stein] See Attachment AR AS. Apache Maven Project [Hervé Boutemy / Christofer Dutz] See Attachment AS AT. Apache OpenOffice Project [Keith McKenna / Zili Chen] No report was submitted. AU. Apache OpenWebBeans Project [Mark Struberg / Christofer Dutz] See Attachment AU AV. Apache OpenWhisk Project [Dave Grove / Shane Curcuru] See Attachment AV AW. Apache Ozone Project [Sammi Chen / Greg Stein] See Attachment AW @Justin Mclean: follow up with VP Privacy on Deep Wiki use AX. Apache Perl Project [Steve Hay / Sander Striker] See Attachment AX AY. Apache Phoenix Project [Istvan Toth / Jean-Baptiste Onofré] See Attachment AY AZ. Apache Pinot Project [Kishore G / Greg Stein] See Attachment AZ BA. Apache POI Project [Dominik Stadler / Emmanuel Lécharny] See Attachment BA BB. Apache Polaris Project [Jean-Baptiste Onofré / Jean-Baptiste Onofré] See Attachment BB BC. Apache Qpid Project [Robbie Gemmell / Justin Mclean] See Attachment BC BD. Apache Ranger Project [Selvamohan Neethiraj / Zili Chen] No report was submitted. BE. Apache RocketMQ Project [Xiaorui Wang / Zili Chen] See Attachment BE BF. Apache Roller Project [Dave Johnson / Christopher Schultz] See Attachment BF BG. Apache Santuario Project [Colm O hEigeartaigh / Sander Striker] See Attachment BG BH. Apache SDAP Project [Nga Thien Chung / Christofer Dutz] See Attachment BH BI. Apache Sedona Project [Jia Yu / Jean-Baptiste Onofré] See Attachment BI BJ. Apache Serf Project [Daniel Sahlberg / Emmanuel Lécharny] See Attachment BJ BK. Apache ServiceComb Project [Zhangjian He / Zili Chen] See Attachment BK BL. Apache ShardingSphere Project [Liang Zhang / Greg Stein] See Attachment BL BM. Apache ShenYu Project [Yu Xiao / Justin Mclean] See Attachment BM BN. Apache SIS Project [Martin Desruisseaux / Shane Curcuru] See Attachment BN BO. Apache Solr Project [Alessandro Benedetti / Shane Curcuru] See Attachment BO BP. Apache Spark Project [Matei Zaharia / Christopher Schultz] See Attachment BP @Christopher Schultz: suggest ways to improve the board report BQ. Apache StormCrawler Project [Richard Zowalla / Zili Chen] See Attachment BQ BR. Apache StreamPipes Project [Philipp Zehnder / Christofer Dutz] See Attachment BR BS. Apache Struts Project [René Gielen / Christopher Schultz] See Attachment BS BT. Apache Subversion Project [Nathan Hartman / Justin Mclean] See Attachment BT BU. Apache Superset Project [Maxime Beauchemin / Sander Striker] See Attachment BU @Shane Curcuru: message all PMCs to improve board reports and discuss "Emeritus" concept for PMCs. BV. Apache Syncope Project [Francesco Chicchiriccò / Jean-Baptiste Onofré] See Attachment BV BW. Apache SystemDS Project [Matthias Boehm / Emmanuel Lécharny] See Attachment BW BX. Apache Tcl Project [Georgios Petasis / Shane Curcuru] No report was submitted. BY. Apache Tez Project [László Bodor / Greg Stein] See Attachment BY BZ. Apache TomEE Project [David Blevins / Greg Stein] No report was submitted. CA. Apache Traffic Server Project [Bryan Call / Sander Striker] See Attachment CA CB. Apache TsFile Project [Jialin Qiao / Greg Stein] See Attachment CB CC. Apache Turbine Project [Georg Kallidis / Emmanuel Lécharny] See Attachment CC CD. Apache Uniffle Project [He Qi / Justin Mclean] See Attachment CD CE. Apache Velocity Project [Nathan Bubna / Zili Chen] See Attachment CE CF. Apache Web Services Project [Daniel Kulp / Christopher Schultz] No report was submitted. CG. Apache Whimsy Project [Dave Fisher / Christofer Dutz] See Attachment CG CH. Apache Xalan Project [Gary D. Gregory / Shane Curcuru] See Attachment CH @Emmanuel Lécharny: roll call for Xalan CI. Apache Xerces Project [Michael Glavassevich / Jean-Baptiste Onofré] No report was submitted. CJ. Apache XML Graphics Project [Clay Leeds / Jean-Baptiste Onofré] See Attachment CJ CK. Apache YuniKorn Project [Wilfred Spiegelenburg / Sander Striker] See Attachment CK Committee reports approved as submitted by General Consent. 7. Special Orders A. Establish the Apache Magpie Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to creation and maintenance of software related to agent-assisted repository maintainership and development, including issue and pull- request triage, contributor mentoring, agent-drafted remediation, developer-side development-cycle skills, and narrowly-scoped fix-and- merge automation. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Magpie Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Magpie be and hereby is responsible for the creation and maintenance of software related to creation and maintenance of software related to agent-assisted repository maintainership and development, including issue and pull- request triage, contributor mentoring, agent-drafted remediation, developer-side development-cycle skills, and narrowly-scoped fix-and- merge automation; and be it further RESOLVED, that the office of "Vice President, Apache Magpie" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Magpie Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Magpie Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Magpie Project: * Andrew Musselman * Amogh Desai * Craig L Russell * Elad Kalif * Pavan Kumar * Ismaël Mejía * James Fredley * Jean-Baptiste Onofré * Justin Mclean * Calvin Kirs * Mike Drob * Paul King * Piotr Karwasz * Jarek Potiuk * Rich Bowen * Evan Rusackas * Russell Spitzer * Zili Chen * Matthew Topol NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jarek Potiuk be appointed to the office of Vice President, Apache Magpie, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7A, Establish the Apache Magpie Project, was tabled. B. Establish the Apache Livy Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the "Apache Livy Project", be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Livy be and hereby is responsible for the creation and maintenance of software related to web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts; and be it further RESOLVED, that the office of "Vice President, Apache Livy" be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Livy Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Livy Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Livy Project: * Alex Bozarth * Arnav Balyan * Asif Khatri * Bikas Saha * Brahma Reddy Battula * Damon Cortesi * György Gál * Imran Rashid * Jean-Baptiste Onofré * Jianzhen Wu * Larry McCay * Luciano Resende * Madhawa Kasun Gunasekara * Marco Gaido * Pralabh Kumar * Shaofeng Li * Shrikant Prasad * Sumit Kumar * Vinod Kumar Vavilapalli * Wing Yew Poon * Xilang Yan NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jean-Baptiste Onofré be appointed to the office of Vice President, Apache Livy, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. RESOLVED, that the Apache Livy Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Livy podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Livy podling encumbered upon the Apache Incubator PMC are hereafter discharged. Special Order 7B, Establish the Apache Livy Project, was approved by Unanimous Vote of the directors present. C. Change the Apache Aries Project Chair WHEREAS, the Board of Directors heretofore appointed Christian Schneider (cschneider) to the office of Vice President, Apache Aries, and WHEREAS, the Board of Directors is in receipt of the resignation of Christian Schneider from the office of Vice President, Apache Aries, and WHEREAS, the Project Management Committee of the Apache Aries project has chosen by vote to recommend Dominik Przybysz (alien11689) as the successor to the post; NOW, THEREFORE, BE IT RESOLVED, that Christian Schneider is relieved and discharged from the duties and responsibilities of the office of Vice President, Apache Aries, and BE IT FURTHER RESOLVED, that Dominik Przybysz be and hereby is appointed to the office of Vice President, Apache Aries, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed. Special Order 7C, Change the Apache Aries Project Chair, was approved by Unanimous Vote of the directors present. 8. Discussion Items 9. Review Outstanding Action Items * Sander Striker: discuss Policy for Inactive Committers with project PMC [ NiFi 2025-10-15 ] Status: https://lists.apache.org/thread/wnph5t6xn9rts4smhtd2gmfpjktyqjv8 * Greg Stein: talk to Pinot PMC about communication channels [ Pinot 2025-11-19 ] Status: will pick this up shortly (did not handle over holidays) * Greg Stein: follow up with TsFile PMC about publishing to PyPI [ TsFile 2025-11-19 ] Status: will pick this up shortly (did not handle over holidays) * Greg Stein: follow up with board about PyPI policy [ TsFile 2025-11-19 ] Status: will pick this up shortly (did not handle over holidays) * Jean-Baptiste Onofré: pursue roll call for XML Graphics [ XML Graphics 2026-01-21 ] Status: Roll call started: https://lists.apache.org/thread/6jnfh77mx8tmjv1m8xgcxv8jnxhllg5h * Zili Chen: follow up about reporting and chair requirements [ RocketMQ 2026-02-18 ] Status: Discussed with the current PMC chair. I'll send the email to private@rocketmq.a.o later. * Shane Curcuru: follow up about licensing [ SIS 2026-02-18 ] Status: In progress: researching issues and contacts. * Kanchana Pradeepika Welagedara: connect with downstream PMCs [ Web Services 2026-02-18 ] Status: * Christopher Schultz: pursue a roll call [ Kylin 2026-03-18 ] Status: Roll call request sent 2026-04-06 https://lists.apache.org/thread/p5vk015gnjdfsm7b81oz6kncx04xnc2p As of Sunday 2026-04-12 2 +1s and a few +0s so far * Jean-Baptiste Onofré: provide template for next board report [ StreamPark 2026-03-18 ] Status: * Justin Mclean: monitor roll call or call for one [ Flagon 2026-04-15 ] Status: * Greg Stein: pursue roll call [ Geronimo 2026-04-15 ] Status: * Emmanuel Lécharny: pursue a roll call [ Lucene.Net 2026-04-15 ] Status: Completed. The role call has been successful: Paul Irwin: +1 Ron Clabo : +1 Shad Storhaug: +1 Shannon Deminick: +1 Prescott Nasser: +0 Elad Margalit: 0 Laimonas Simutis: 0 Simon Svensson: 0 So we have at least 4 PMC active members, plus 4 other following the PMC mailing list. I wish we get a report this month after 3 misses. (and actually, we did ;-) * Zili Chen: follow up about project viability [ MADlib 2026-04-15 ] Status: Follow up - https://lists.apache.org/thread/781rspl421vcmclzjdqlstzq8b5vgf4m Seems MADlib didn't reply to Cloudberry's collaboration suggestion. * Justin Mclean: follow up about contributor [ PDFBox 2026-04-15 ] Status: * Christofer Dutz: follow up on dev list about viability [ Rya 2026-04-15 ] Status: Sent a follow up email to private@ (on 17th of Mai) ... had missed this AE and therefore it's probably too late for results in this meeting, just keep it open and assigned to me. * Zili Chen: follow up about board report [ SkyWalking 2026-04-15 ] Status: Notified. https://lists.apache.org/thread/k14s7vyb5tyxoq7kkwhgxqk6cvgk7052 * Justin Mclean: look into contributor issue [ Wayang 2026-04-15 ] Status: 10. Unfinished Business 11. New Business 12. Announcements 13. Adjournment Adjourned at 22:03 UTC ============ ATTACHMENTS: ============ ----------------------------------------- Attachment 1: Report from the VP of Brand Management [Mark Thomas] Covering the period April 2026 * ISSUES FOR THE BOARD One of the documents regularly required to progress trademark matters is a Certificate of Good Standing for Apache. However, when counsel last submitted the Certificate request to the Delaware Secretary of State (DE SOS), DE SOS records showed that Apache is not in good standing: the entity is in a status of: AR Delinquent tax due - for the 2025 annual report not being filed in time, which was due by March 1st. This is currently blocking the transfer of the SEATA trademark. I raised the issue with the president and the treasurer on 2026-05-05 and have yet to receive a response. * OPERATIONS Daan Hoogland continues to provide some very welcome assistance with trademark issues. Responded to the following queries, liaising with projects as required: - A request to use the FLINK logo on some conference swag - Provided informal advice that STEWARD was not a good name for a new PMC - A request to use the POI logo in a BSc thesis - A request to use the CLOUDSTACK logo for a conference booth - A request to use the FLINK mark for a conference - A request to use the FLUSS mark for a conference * REGISTRATIONS The logo registration is progressing. The SUPERSET application has been submitted. The renewal of OFBIZ in the US has been submitted. The renewal of CASSANDRA in the US has been submitted. Transfer of the SEATA trademark is currently blocked. See above. * INFRINGEMENTS A potential conflict with FLEX was discussed with the FLEX PMC and the decision taken to take no further action. The potential infringement of KAFKA has been resolved. The potential infringements of the the GRAVITINO mark have been resolved. No progress for the SPARK PMC in addressing a range of product naming issues with multiple 3rd parties. No progress regarding a site with a possible infringement of APISIX. No further progress regarding the downstream vendor with multiple infringements of ASF marks. The XMLGRAPHICS PMC is progressing a complaint with GitHub regarding a potential third-party infringement of FOP. No progress from the GLUTEN PMC to address a range of product naming issues with multiple 3rd parties. There remains one issue with IOTDB to be solved. ----------------------------------------- Attachment 2: Report from the VP of Fundraising [Bob Paulin] 1) ASF Sponsors: a —New: two companies that have made qualifying corporate contributors to the ASF are considering recognition as ASF Sponsors. b —Renewals: we are pursuing one Gold-level renewal, as well as two Bronze renewals. c —Payments: 1 —New: we received two corporate contributions: one would receive recognition at the Platinum level, and the other Silver, should they wish to be publicly recognized. 2 —Received: we received Sponsorship renewal payments from two Gold Sponsors. 3 —Incoming: we await renewal payments from two Platinum, two Gold, and one Bronze Sponsor. 2) Targeted Sponsors: we have updated and renewed a Platinum-level Targeted Sponsorship, and are working on the Tooling Initiative’s FY2027 funding plans, including onboarding a new Platinum-level backer. a - Fundraising requests the board's attention related to Apache Logging PMC's request [1] to use Targeted Sponsorship Fund for some items defined in the Targeted Policy that "have merit to be discussed further" [2]. As has long been the case the ASF has not engaged in anything that might be viewed as "Paying for development" in our projects. Would like the board's guidance on if these specific circumstances might be exempt. Additionally while the amounts are a small portion of the Foundations earnings what follow up work might be needed to avoid these payments from being considered a private benefit or inurement [3] i. Paying for security triage (PMC Members) ii. Paying Release Managers (PMC Members) iii. Paying for Documentation (PMC Members) 3) Sponsor Relations: we facilitated the ASF’s largest corporate charitable contribution, and used those funds to seed the ASF’s new Responsible AI Initiative. https://news.apache.org/foundation/entry/the-apache-software-foundation-launches-10m-responsible-ai-initiative-with-initial-1-75m-donation 4) Event Sponsorship: we continue to process sponsorships for 2026 for Community Over Code Europe as well as Lakehouse Day, and promote opportunities for both Community Over Code Europe and Asia events. 5) Individual Donations and Corporate Giving: we received a corporate charitable contribution for $1.5MM, which is the largest single cash contribution that the ASF has received to date. In addition, we received $2,002 in online donations via https://donate.apache.org/ . 6) Administrivia: our work with the ASF Infrastructure, Treasury, and Marketing & Publicity teams continues as our activities expand for the new fiscal year. [1] https://lists.apache.org/thread/39p8ls06n2g21xcqnk96cmz60fhh0oyz [2] https://apache.org/foundation/docs/targeted-sponsorship-policy.html [3] https://www.congress.gov/crs-product/R48873 ----------------------------------------- Attachment 3: Report from the VP of Marketing and Publicity [Brian Proffitt] Special note to thank the M&P team for the incredible work they accomplished in April, 2026. There was a lot of content and coordination happening around embargoed news, and the team handled everything admirably. Foundation Comms * Produced and issued April issue of Plus One newsletter * Subscriber list now totals 3,644 (537 new subscribers in March) * Total sent: 3,100 | Unique opens: 337 | Open rate: 11% * Published blog announcing new ASF members and Daniel Ruggeri as Board of Directors EVP * Coordinated with Anthropic PR team and ASF Fundraising to issue a press release touting Anthropic’s $1.5m donation to The ASF * Coordinated with Anthropic and Alpha-Omega’s PR teams to develop and issue a press release launching The ASF’s Responsible AI Initiative * Developed blog with Piotr P. Karwasz to highlight the CRA Monday’s webinar he hosted to illustrate what the Apache Logging team has done post-Log4Shell to be CRA-ready * Coordinated with Priya Sharma to develop GSoc Blog * Coordinated with Greg Stein on OSS elections blog * Sourced information from Dave Fisher and coordinated with Alpha-Omega’s PR team to develop maintainer-focused case study blog to highlight work done 1 year into The ASF’s Tooling Initiative * Began development of FY26 annual report, including data sourcing and ASF leadership outreach * Began coordination between ASF fundraising and Google to determine M&P sponsor benefits to pursue, such as a Success at Apache blog spotlight * Began coordination between ASF fundraising and M&P on new targeted sponsor and possible press announcement * Secured interview opportunity with TFiR to discuss Responsible AI initiative; scheduling in process * Developed in-depth blog in collaboration with Jinwoo Hwang (Apache Geode) and The ASF Security team to spread awareness around the Public CA clientAuth EKU Sunset Project Comms * Published and promoted project spotlight blog featuring Apache Iceberg * Published and promoted blog showcasing OpenSource4You (ALC Taipei) and the next generation of Apache Mahout contributors. Digital * Continued development and coordination for C/C website * Continued running digital ads to promote C/C, including TAC post boost Brand Project * Continued coordination with graphic designer to re-design event branding to better align with new ASF logo * Coordinated between security team and graphic designer to develop updated Security team logo Social Media Overview The highest performing pieces of content for April include project news, Daniel Ruggeri’s appointment, and the Apache Iceberg spotlight. Social Media Overview The highest performing pieces of content for April include project news, Daniel Ruggeri’s appointment, and the Apache Iceberg spotlight. Social Highlights (X + Bluesky + Fosstodon + LinkedIn)* * Total Audience: 149,107 * X: 66,154 * Bluesky: 1,083 * Fosstodon: 205 * LinkedIn: 81,665 * Total Posts: * X/Bluesky/Fosstodon: 29 * LinkedIn: 16 * Total Engagements: 4,890 *Bluesky analytics are still hard to get consistently without paying for a separate service. As of March 2026, reporting also includes Fosstodon. We hope Buffer will enhance reporting capabilities in the near future so that ASF social reporting is more comprehensive. Website Analytics * 802,620 visits, 802,504 unique visitors +1.5% * 2 min 26s average visit duration -6.4% * 63% visits have bounced (left the website after one page) +3.3% * 2.3 actions (page views, downloads, outlinks, internal site searches) per visit -8% * 1,393,642 pageviews, 971,811 unique pageviews -2.4% * 21 total searches on your website, 10 unique keywords +75% * 116,650 downloads, 85,463 unique downloads -53.9% * 302,691 outlinks, 182,554 unique outlinks -4.9% ----------------------------------------- Attachment 4: Report from the VP of Infrastructure [Danny Angus] General ------- No issues currently require the Board's attention. Budget ------ VP Infra has provided the board with clarification on Infra's 2026/27 budget. MFA Efforts ----------- MFA soft-launch is ongoing with no service issues reported. The procedure began 2 April. Other News ---------- Atlassian Cloud migration testing continues. There have been some hurdles to cross, license renewal issues on the Cloud side and changes to the migration tooling and workflow, that have delayed progress this month. Therefore our estimate to completion remains at 3 months from now, if all goes well. Infra collaborated with the Security Team to strengthen baseline security for all projects using Git (Gitbox and GitHub) by proposing a series of security-feature Pull Requests to the .asf.yaml service file. Each affected project was individually notified by email of our intentions, rationale, and proposed plan. A sample email: https://lists.apache.org/thread/f3x6756ypp8cw9r93xopbdl6029yhksv Community News -------------- Roundtable: Infra's next Roundtable will be June 3, 1700 UTC. Piotr P. Karwasz will present on release automation. See https://infra.apache.org/roundtable for how to join the Roundtable channel and take part in the monthly meetings. Community over Code: Infra will be sharing a series of presentations and events at Community Over Code Glasgow, ranging from an IRL roundtable to the ever-popular Infra 101, to Games Night, which was a huge success at the 2025 event. ----------------------------------------- Attachment 5: Report from the VP of Tooling [Dave Fisher] ## Tooling ### Apache Trusted Releases (ATR) We are finishing all of the UI improvements and moving towards an Alpha3 by the end of this month and then Beta by the end of June. ### Board Agenda Tool (BAT) We will need to discuss next improvements with the board. ----------------------------------------- Attachment 6: Report from the VP of Conferences [Brian Proffitt] All notices for acceptances have gone out for Community Over Code Glasgow 2026. An extra room has been acquired to host security workshops and ASF project hackathons. The co-located Lakehouse Day organized by Danica Fine is also proceeding well. Community Over Code Asia is on schedule for August 7 to 9，2026 in Beijing, China. TAC applications are now being accepted for this event. Work is still ongoing with the web team to update and expand communityovercode.org. The planning team has tentatively secured a venue for the 2027 North America Community Over Code. An announcement will be made during the Glasgow event. ----------------------------------------- Attachment 7: Report from the Apache Travel Assistance Committee [Gavin McDonald] Current Events =============== Community Over Code Glasgow --------------------------- We had an initial mid-applications open period judging round, and accepted and notified 12 people in this first of two judging rounds. The idea is to allow those that applied early in order to apply for Visas or other reasons for applying early were notified earlier than the June cut-off date. The remaining 24 of the initial 36 applicants will be pooled in with those that apply after the initial judging date. Applications for this event close on the 3rd June. Community over Code Asia - Beijing ---------------------------------- Applications for Beijing close on the 31st May, we have a dozen or so applications in so far. Monthly Meetings ================ Trying to organize a meeting date to suit everyone. Future Events ============= None currently Short/Medium Term Priorities ============================ Keeping an eye out for other smaller events to support. Berlin Buzzwords is one we have supported before and if we have budget would like to have some people attend that one. Post surveys for Bratislava, Hangzhou, Denver, Beijing and Minneapolis still to be done. Mailing List Activity ===================== Not much activity for April/May other than notice of the Glasgow midway judges call Membership ========== No changes to the Committee this month. ----------------------------------------- Attachment 8: Report from the VP of Diversity and Inclusion [Daniel Gruno] ----------------------------------------- Attachment 9: Report from the VP of Data Privacy [Christian Grobmeier] ----------------------------------------- Attachment 10: Report from the VP of Public Affairs [Dirk-Willem van Gulik] Nothing to report - things moving along as expected. Standards still largely lost in action - and some things, such as the implementing act, are more delayed than is ideal. ----------------------------------------- Attachment 11: Report from the VP of ECMA Relations [Piotr Karwasz] Work in all ECMA TC-54 committees is continuing. After months of discussion, the question of whether the ASF should define its own Package URL type (`asf`) or adopt the emerging `sid` type appears to be approaching resolution. At the most recent TG-2 meeting, consensus formed around identifiers of the form: ``` pkg:sid/apache.org/... ``` See https://github.com/package-url/purl-spec/issues/834 for context. The `sid` type has two subtypes. The commercial software subtype has stalled pending industry feedback, but the domain-based subtype is mature enough to be ratified in the near term if the ASF needs it. ----------------------------------------- Attachment 12: Report from the VP of W3C Relations [Andy Seaborne] ----------------------------------------- Attachment 13: Report from the Apache Legal Affairs Committee [Roman Shaposhnik] Past month has been pretty calm. Committee members took good care of resolving most issues on time. After resolving many of LEGAL issues, we are at a dramatic 3 open issues right now. VP Legal announced his intent to resign and kicked-off a follow-on process on the legal-private: https://lists.apache.org/thread/mmd4sg4bjx5bxvlc0h52ldcl8qyqh9nz ----------------------------------------- Attachment 14: Report from the Apache Security Team Project [Mark J. Cox] April * The load of incoming security reports continues to grow significantly, leaving limited time for other responsibilities. We plan improved tooling to more effectively handle issues. We have also taken on another part-time contractor from March 1st which will help considerably. * Worked together with Infra to respond to the breach of a 3rd-party component, Axios (https://www.upwind.io/feed/from-nodes-to-snakes-npm-supply-chain) * Worked together with Infra to respond to an incident that, after much effort by many involved, turned out to be a false positive. * Decided to stop participating in 3rd-party bug bounty program huntr.com (details at https://security.apache.org/huntr/) Stats for April 2026: 25 [support request/question not security notification] 20 [license confusion] 19 [report/question relating to dependencies] Security reports received: 515 (last months: 386, 200, 160, 98) 28 ['tomcat'] 25 ['airflow'] 23 ['httpd'] 21 ['activemq'] 18 ['camel'] 17 ['arrow', 'superset', 'zookeeper'] 15 ['iotdb', 'kafka', 'storm'] 13 ['website or other infrastructure'] 11 ['flink', 'guacamole', 'shenyu', 'skywalking', 'spark'] 10 ['doris'] 9 ['commons', 'solr'] 7 ['beam', 'fineract', 'rocketmq', 'seatunnel'] 6 ['apisix', 'hadoop', 'hugegraph', 'nifi', 'thrift'] 5 ['dolphinscheduler', 'kvrocks', 'mina', 'polaris', 'roller', 'trafficserver', 'zeppelin'] 4 ['cloudstack', 'dubbo', 'openserverless', 'qpid', 'seata', 'syncope', 'ws', 'xmlgraphics'] 3 ['axis', 'nutch', 'opennlp'] 2 ['artemis', 'brpc', 'casbin', 'grails', 'hive', 'kylin', 'livy', 'logging', 'maven', 'ofbiz', 'openmeetings', 'pdfbox', 'pulsar', 'ranger', 'shiro', 'streampipes', 'velocity'] 1 ['allura', 'answer', 'archiva', 'avro', 'brooklyn', 'burr', 'calcite', 'couchdb', 'datasketches', 'druid', 'echarts', 'empire-db', 'fluss', 'fory', 'geode', 'groovy', 'hbase', 'hc', 'httpcomponents', 'hudi', 'inlong', 'jmeter', 'kyuubi', 'linkis', 'mynewt', 'openjpa', 'openoffice', 'ozone', 'plc4x', 'pouchdb', 'royale', 'servicecomb', 'shardingsphere', 'singa', 'struts', 'subversion', 'tika', 'tvm', 'wicket', 'xalan'] In total, as of 1st May 2026, we're tracking 856 (last months: 629, 440, 359) open issues across 138 projects, median age 44 days (last months: 47, 64, 79). 180 of those issues have CVE names assigned. 32 (last months: 28, 22, 25) of these issues, across 14 projects, are older than 365 days. * openoffice (Health red): Several issues in OpenOffice are over 365 days old. They are not severe enough to warrant stopping distribution of OpenOffice. (Last update: 2026-05-06) * fineract (Health amber): there is one remaining open issues that is over a year old, and quite a few untriaged. The PMC is making progress with documentation, architectural changes and expanding the team, but not yet out of the weeds. (Last update: 2026-05-06) * spark (Health amber): the project has a backlog of security reports to be triaged (Last update: 2026-05-06) * superset (Health amber): while the project is actively publishing fixes to security issues each release, there is concern about a growing backlog. (Last update: 2026-03-03) ----------------------------------------- Attachment A: Report from the Apache AGE Project [Jeff Jirsa] ----------------------------------------- Attachment B: Report from the Apache Airavata Project [Suresh Marru] ## Description: The mission of Apache Airavata is the creation and maintenance of software related to executing and managing computational jobs on distributed computing resources, including local clusters, supercomputers, national grids, academic and commercial clouds. ## Project Status: Current project status: The community remains small and healthy. Issues for the board: No issues to report. ## Membership Data: Apache Airavata was founded 2012-09-18 (14 years ago) There are currently 46 committers and 28 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Yasith Jayawardana on 2025-04-06. - No new committers. Last addition was Ganning Xu on 2025-04-09. ## Project Activity: The Airavata Custos repository, mailing lists, github has significant activity. Anticipating some focused attention and broadening the community of this component. ## Community Health: Three GSoC students were selected, and with the new energy, hoping to improve communications on board documentation simplification. Aiming to induct new committers/PMC members to increase momentim. ----------------------------------------- Attachment C: Report from the Apache Ambari Project [Brahma Reddy Battula] ## Description: The mission of Apache Ambari is the creation and maintenance of software related to Hadoop cluster management ## Project Status: Current project status: Dormant Issues for the board: none ## Membership Data: Apache Ambari was founded 2022-06-15 (4 years ago) There are currently 23 committers and 19 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 Jialiang Cai on 2025-04-26. - Sandeep Kumar was added as committer on 2026-02-24 ## Project Activity: Recently 3.0.0 was released on 2025-04-06.Later all bug fixes happening. ## Community Health: There is a slow down in web development but consistent.Will focus on improvement ----------------------------------------- Attachment D: Report from the Apache Ant Project [J Pai] ----------------------------------------- Attachment E: Report from the Apache Artemis Project [Christopher L. Shannon] ## Description: The mission of Apache Artemis is the creation of a high-performance, multi-protocol open source messaging platform designed to power modern microservices and cloud-native applications. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Artemis was founded 2025-11-18 (5 months ago) There are currently 64 committers and 30 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Andy Taylor on 2025-12-10. - No new committers. Last addition was Adrian T. Co on 2025-12-03. ## Project Activity: Apache Artemis 2.54.0 is upcoming and planned to be released shortly. Releases: * Apache Artemis Console 1.8.0 was released on 2026-04-30. * Apache Artemis 2.53.0 was released on 2026-03-20. * Apache Artemis Console 1.7.0 was released on 2026-03-11. * Apache Artemis 2.52.0 was released on 2026-03-02. * Apache Artemis 2.51.0 was released on 2026-02-11. * Apache Artemis Console 1.6.0 was released on 2026-02-03. ## Community Health: The community is healthy and there continues to be little impact to users as everything transitions to the new TLP. ----------------------------------------- Attachment F: Report from the Apache Avro Project [Ryan Skraba] ## Description: Apache Avro is a data serialization system with a compact binary format. It is used for storing and transporting schema-driven serialized data. The unique features of Avro include automatic schema resolution: when the reader's expected schema is different from the actual schema with which the data was serialized the data is automatically adapted to meet reader's requirements. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Avro was founded 2010-04-21 (16 years ago) There are currently 39 committers and 25 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Oscar Westra van Holthe - Kind on 2024-08-27. - Mattia Basone was added as committer on 2026-03-20 ## Project Activity: We didn't have any release this quarter, but the preparation for the next minor release is well underway, focusing on accumulated bug and security fixes. There's been some good progress for features and improvements on the main branch and we should definitely continue the momentum with a major release immediately after. Our experience has always been that it's difficult to do a release after a long period of inactivity. We raised a issue last quarter about declining PMC and committer engagement, but it seems that interest is up with the upcoming release. ## Community Health: Mailing Lists: - dev@avro.apache.org had 472 emails (+6% change) - issues@avro.apache.org (mostly notifications) had 800 emails (-6% change) - user@avro.apache.org continues to have very little traffic, 6 total JIRA: - 18 issues opened (-51% change) - 7 issues closed (-73% change) Code Repository: - 199 commits in the past quarter (+99% change) - 22 code contributors in the past quarter (+29% change) GitHub: - 226 PRs opened on GitHub, past quarter (+105% change) - 220 PRs closed on GitHub, past quarter (+71% change) A lot of the release work was bumping dependencies and cherry-picking existing fixes into the next release branch, which explains why the number of bugs fixed is quite low while GitHub activity is fairly high. There's been a significant number of issues fixed after the reporting period. ----------------------------------------- Attachment G: Report from the Apache BookKeeper Project [Enrico Olivelli] ## Description: The mission of BookKeeper is the creation and maintenance of software related to Replicated log service which can be used to build replicated state machines ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache BookKeeper was founded 2014-11-19 (11 years ago) There are currently 32 committers and 20 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - No new PMC members. Last addition was Shiji Lu on 2025-05-14. - No new committers. Last addition was Zhangjian He on 2025-01-27. ## Project Activity: In the past months we have lot of activity in the codebase, both for small improvements but also new features. Recent releases: 4.16.7 was released on 2025-07-07. 4.17.2 was released on 2025-07-07. 4.16.6 was released on 2024-06-26. We are also going to cut a new release from the 4.17 release line, and problably also for other active release branches. ## Community Health: There is not much activity in the mailing list, but actually in the past months we have more messages that usual. There are some conversations on the Bookkkeper slack workspace, but they are almost only pings about asking for reviews or votes on releases. Community is doing well, and we have some contributions from users that are not committers, altough most of the contributions come from existing committers. We don't have candidates for commitership in the short term yet. Overall we are doing well ----------------------------------------- Attachment H: Report from the Apache Brooklyn Project [Juan D. Cabrerizo] ## Description: The mission of Apache Brooklyn is the creation and maintenance of software related to a software framework for modeling, monitoring and managing cloud applications through autonomic blueprints. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Brooklyn was founded 2015-11-18 (10 years ago) There are currently 20 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Iuliana Cosmina on 2021-06-04. - No new committers. Last addition was Mykola Mandra on 2022-03-08. ## Project Activity: Improvements in security suppressing secrets in complex JSON serializable types We have opened new Pull Requests (PRs) focusing on improving log access security and mitigating potential vulnerabilities that were reported to the ASF security team. ## Community Health: Our primary focus remains on addressing user needs and incorporating feedback We are currently investigating recent security reports from the security team to determine the actual impact and develop mitigation strategies without disrupting expected functionality. Responses to these reports are forthcoming. ----------------------------------------- Attachment I: Report from the Apache BuildStream Project [Abderrahim Kitouni] ## Description: The mission of Apache BuildStream is the creation and maintenance of software related to efficiently and correctly developing, building and integrating software stacks ## Project Status: Current project status: Ongoing (low activity) Issues for the board: None ## Membership Data: Apache BuildStream was founded 2022-09-21 (4 years ago) There are currently 6 committers and 6 PMC members in this project. The Committer-to-PMC ratio is 1:1. Community changes, past quarter: - No new PMC members. Last addition was Abderrahim Kitouni on 2022-09-21. - No new committers were added. ## Project Activity: A short reporting period (1 month) because the previous reports were late. A few bugfixes landed in master, no new release. ## Community Health: * Some discussion on the mailing list, including interest in updating the website / documentation. * A new project using BuildStream released their first alpha: https://docs.projectbluefin.io/blog/dakota-alpha-1/ * BuildStream packaged in Debian: https://lists.apache.org/thread/gh7cyf135d61921c421kl1lvtcwnh3h8 ----------------------------------------- Attachment J: Report from the Apache BVal Project [Matt Benson] ## Description: The mission of BVal is the creation and maintenance of software related to Apache BVal: JSR-303 Bean Validation Implementation and Extensions ## Project Status: Current project status: Dormant Issues for the board: none ## Membership Data: Apache BVal was founded 2012-02-14 (14 years ago) There are currently 17 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 9:8. Community changes, past quarter: - No new PMC members. Last addition was Jean-Louis Monteiro on 2020-11-29. - No new committers. Last addition was Markus Jung on 2024-07-08. ## Project Activity: The usual thrum of dependency upgrades has continued; we have also, for a change, seen a fair number of performance-focused and other minor improvements made to BVal's codebase recently. Note from the chair: please accept my apology for having missed the report date these past two months. ## Community Health: The recent spike in commit activity has been on the part of a single project member, but the response from other project members has been demonstrative of our continued state of readiness. ----------------------------------------- Attachment K: Report from the Apache Cassandra Project [Ekaterina Dimitrova] Are you able to provide adequate oversight of your project? That is, are there at least three PMC members who are engaged enough to respond in the event of a CVE or similar crisis? Yes, we maintain adequate project oversight and can address CVEs. Twenty-four PMC members responded to the last roll call. Numerous PMC members actively participate in both dev and private list discussions, ensuring that we have more than the requisite three members available for rapid response to a CVE or similar event. Are there current or upcoming risks that threaten the sustainability of your project? This could be anything from a change in employment of prolific contributors, to an acquisition affecting a significant corporate contributor, to a change in the technology landscape that makes your project less (or more) relevant. We currently do not see any specific risks threatening the project's sustainability. We are focused on long-term health through deliberate diversification and expansion of our contributor base. We just added 1 new PMC member and 3 new committers to the project. Additional indicators of Project Health and Growth this Quarter: Releases: We shipped new versions of the: Cassandra server; Java, GoCQL and Python drivers; Cassandra sidecar; Cassandra analytics; Our next major Cassandra release got its first alpha. Community: The project will have its own track at Community over Code EU 2026. There was a strong submission participation. We managed to fill a three-day schedule and still have certain submissions wait-listed. The project will also support the GSOC program. We already have registered mentors and projects for a few interested students. What can the Foundation do to more effectively make your project more successful in its mission of providing software for the public good? Nothing at this point. ----------------------------------------- Attachment L: Report from the Apache Celeborn Project [Keyong Zhou] ## Description: The mission of Apache Celeborn is the creation and maintenance of software related to an intermediate data service for big data computing engines to boost performance, stability, and flexibility ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Celeborn was founded 2024-03-20 There are currently 27 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Fei Wang on 2024-12-31. - Erik Fang was added as committer on 2025-12-03. ## Project Activity: Software development activity: - Release 0.6.3 is released on 23 April. - Release 1.0.0 is under discussion. - CIP-13 Support auto scaling is under development. - CIP-19 Support app priority is under development. - CIP-20 Dynamically optimize shuffle write parallelism is under development. - CIP-21 Support Flink JM failover is under discussion. - CIP-22 Encryption at Rest for Celeborn Shuffle Data is under discussion. - Celeborn Web UI is under discussion. - Support Ray is under discussion. Recent releases: - Release 0.6.3 is released on 23 April. ## Community Health: Overall community health is good. In the past quarter, the dev mail list mail number had a 29% increase in the past quarter. The issues mail list had a 52% decrease to 820. We have been performing extensive outreach for our users, and encouraging them to contribute back to the project. Also, we are active in making a voice in various conferences to attract more users. ----------------------------------------- Attachment M: Report from the Apache Community Development Project [Swapnil Mane] ## Description: The mission of Community Development the creation and maintenance of resources, tools, and advice to help ASF Projects grow and retain their project communities. ## Project Status: Current project status: Ongoing with high activity Issues for the board: None ## Membership Data: Apache Community Development was founded 2009-10-31 (17 years ago) There are currently 54 committers and 44 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - Jarek Potiuk was added to the PMC on 2026-05-01 - Jude Smith was added as committer on 2026-03-11 - Jarek Potiuk was added as committer on 2026-05-03 ## Project Activity: ### Google Summer of Code 2026 GSoC 2026 is well underway. We were accepted as a mentoring organization and have been actively managing proposal ranking, mentor approvals, and project slot allocations. The mentors@ list saw 141 messages across 40 threads this quarter, reflecting strong engagement from mentors and prospective contributors. Priya Sharma continues to lead GSoC administration. ### GitHub Repository Activity A new comdev repository (github.com/apache/comdev) was created this quarter, housing tooling to help projects summarize their activity, as well as MCP Model Context Protocol) servers for querying ASF data sources such as mailing list archives and project metadata. The Community.apache.org website began a monthly cadence of blog posts highlighting community growth (new committers and PMC members across the Foundation), releases, and project birthdays. (https://community.apache.org/blog) Events.apache.org added new infrastructure to coordinate volunteer activity for Community Over Code. https://events.apache.org/events/2026 ## Community Health: The project is in good health. We are attracting new contributors who are making meaningful contributions quickly, and our GSoC pipeline continues to draw strong mentor and student engagement. The shift toward building developer tooling (MCP servers, project activity summarization) represents a new direction for ComDev beyond documentation and events, and has already attracted outside contributions with security and CI improvements. The dev@ list remains active with substantive discussions rather than just administrative traffic. ----------------------------------------- Attachment N: Report from the Apache CouchDB Project [Jan Lehnardt] ----------------------------------------- Attachment O: Report from the Apache Creadur Project [Philipp Ottlinger] ## Description: The mission of Creadur is the creation and maintenance of software related to Comprehension and auditing of software distributions ## Project Status: Current project status: ongoing Issues for the board: none ## Membership Data: Apache Creadur was founded 2012-04-18 (14 years ago) There are currently 11 committers and 10 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 Claude Warren on 2024-01-23. - No new committers. Last addition was Jean-Baptiste Onofré on 2024-01-23. ## Project Activity: After the release of RAT 0.18 development on 1.0 continues in the background, while other activities remain relatively low. ## Community Health: No changes in community health have been observed. Development is currently focused on RAT 1.0. There is no explicit plan to increase interest in RAT. Previously, I raised the question of whether RAT tooling should become part of the release tooling process or be incorporated into the ASF tooling project. The work on version 1.0 enables a more flexible approach to integrating RAT into other build and ecosystem tools. As a result, the Gradle integration remains open and is awaiting the 1.0 release before being published in a more granular form. ----------------------------------------- Attachment P: Report from the Apache DataFu Project [Eyal Allweil] ## Description: The mission of Apache DataFu is the creation and maintenance of software related to well-tested libraries that help developers solve common data problems in Hadoop and similar distributed systems ## Project Status: Current project status: Dormant Issues for the board: None ## Membership Data: Apache DataFu was founded 2018-02-21 (8 years ago) There are currently 20 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 5:3. Community changes, past quarter: - No new PMC members. Last addition was Ohad Raviv on 2023-02-06. - No new committers. Last addition was Ben Rahamim on 2025-02-19. ## Project Activity: Most of the ongoing efforts were stalled in the past quarter. The blog post is delayed because of scheduling problems with PayPal (with whom we wanted to copublish, like we did previously). We will probably do a minor release just to support another Spark version - there's a new contributor who has expressed interest in this. ## Community Health: As written above, a relatively dormant quarter. Some discussions about the next release and blog, mostly on Jira and comments in GitHub, but nothing substantial. ----------------------------------------- Attachment Q: Report from the Apache DataSketches Project [Lee Rhodes] ## Description: The mission of Apache DataSketches is the creation and maintenance of software related to an open source, high-performance library of streaming algorithms commonly called "sketches" in the data sciences. Sketches are small, stateful programs that process massive data as a stream and can provide approximate answers, with mathematical guarantees, to computationally difficult queries orders-of-magnitude faster than traditional, exact methods ## Project Status: Current project status: Ongoing and growing activity Issues for the board: none ## Membership Data: Apache DataSketches was founded 2020-12-15 (5 years ago) There are currently 23 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Zili Chen on 2026-01-05. - Zejiong Dong was added as committer on 2026-03-11 ## Project Activity: Two recent releases that were not previously recorded in the database: datasketches-rust-0.2.0 on Jan 13, 2026 datasketches-go-v0.1.0 on Mar 27, 2026 Future releases that are in the works include: Rust, Go, Memory, and Java. ## Community Health: Our project is healthy. We have a small, loyal and growing community of users that contact us when they have questions or issues. We are experiencing growing interest from major corporations in our multi-language libraries. We continue to get interest from scientists around the world who offer ideas for new sketches for our library based on recent research and consult with us on improving the mathematical rigor of our sketches. ----------------------------------------- Attachment R: Report from the Apache DeltaSpike Project [Mark Struberg] ## Description: Apache DeltaSpike is a suite of portable CDI (Contexts & Dependency Injection) extensions intended to make application development easier when working with CDI and Java EE. Some of its key features include: - A core runtime that supports component configuration, type safe messaging and internationalization, and exception handling. - A suite of utilities to make programmatic bean lookup easier. - A plugin for Java SE to bootstrap various CDI containers. - JSF integration - JPA integration and transaction support. - A Data module, to create an easy to use repository pattern on top of JPA. - Testing support to allow low level unit testing of CDI enabled projects. ## Issues There are no immediate issues requiring board attention at this time. Still low activity, but slowly boosting activity again. ## Activity We did some updates and cleanup in our code. We've now also added a new test-control5 module for supporting junit5 and 6. The plan is to release this soonish. Our main focus is on backward compatibility and fixing bugs. We do intentionally NOT rewriting stuff without a urgent need. ## Community changes, past quarter: - No new PMC members. Last addition was Harald Wellmann on 2016-05-19. - Thomas Frühbeck was added as committer on 2024-02-05 ## Recent releases: - 2.0.1 (JakartaEE) was released on 2025-08-11. - 2.0.0 (JakartaEE) was released on 2024-04-10. - 1.9.6 was released on 2022-04-12. ----------------------------------------- Attachment S: Report from the Apache Doris Project [Mingyu Chen] ## Description: The mission of Apache Doris is the creation and maintenance of software related to a MPP-based interactive SQL data warehousing for reporting and analysis ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Doris was founded 2022-06-14 (4 years ago) There are currently 99 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 7:2. Community changes, past quarter: - Calvin Kirs was added to the PMC on 2026-04-23 - Han Bao was added as committer on 2026-03-16 - Yuwei Chang was added as committer on 2026-04-28 - Zhengyu Zhang was added as committer on 2026-04-20 - Si Wu was added as committer on 2026-02-25 - Yiteng Su was added as committer on 2026-04-28 - Yan Xuecheng was added as committer on 2026-04-10 - Zhang Dong was added as committer on 2026-02-26 ## Project Activity: Apache Doris has had a busy three months on the release front. The community shipped the 4.0.4 maintenance release in early March, followed shortly by 4.0.5, both rolling up a large number of bug fixes and stability improvements on the 4.0.x line — particularly around cloud mode, the streaming insert / CDC subsystem, and the new TIMESTAMPTZ data type. In parallel, 4.1.0-rc01 was cut, kicking off the formal release candidate cycle for the next minor version. Beyond maintenance, the project is making meaningful headway on several strategic directions: - AI-native data: introduction of a Rust-based Lance format reader for AI-native datasets, support for multimodal (file) embeddings, BM25 scoring in the inverted index query engine, and a new on-disk IVF ANN index type for vector search. - Streaming & CDC: the new StreamingInsertJob framework continued to mature, picking up MySQL/PostgreSQL CDC sources, a cdc_stream TVF, per-job metrics, auto-resume controls, SSL support, and the ability to target specific compute groups. The dynamic table feature also landed in two parts — first the meta/DDL layer, then the streaming query and consumption infrastructure. - Lakehouse & external catalogs: Iceberg gained REST + S3Tables IAM-role auth, v3 row lineage, and a working MERGE INTO implementation; Paimon picked up JDBC catalog support; and the FE catalog layer was refactored behind a new fe-connector SPI plugin framework, with JDBC and ES catalogs migrated onto it. - Authentication & multi-tenancy: end-to-end OIDC integration with a MySQL login bridge and role mapping, a multi-root auth plugin loader, a ClusterGuard SPI for cluster-level policy enforcement, and IAM-role auth for Routine Load and S3 filesystem access. - Performance & engine work: a global Timestamp Oracle (TSO) for monotonic timestamps, bucketed aggregation operators, multi-level partition spilling, outer join reorder in DPhyper, ASOF join, adaptive memtable flush, adaptive scan batch sizes, and broad memory accounting cleanup. - Operability: new ADMIN COMPACT TABLE TYPE='FULL' (also enabled in cloud mode), a CompactionTaskTracker system table + HTTP API, file-cache admission control, condition cache for external tables, and richer profiling for scans, joins, and sync-rowset paths. On the community side, the project also continues to invest in contributor experience — adding fast incremental FE compilation tooling, a docker-based regression-test skill, AI-assisted code review hooks in CI, and tightening committer-only triggering for protected pipelines. ## Community Health: Overall community health remains strong. Over the last quarter Apache Doris saw contributions from roughly 80 distinct committers and contributors across FE, BE, cloud, docs, and CI infrastructure, with about 11 first-time contributors landing their first commits during the period — a healthy and steady inflow of new faces. The committer pool itself also continues to grow: a new collaborator was onboarded this quarter, reflecting ongoing investment in mentoring active contributors toward committership. The dev@doris.apache.org and users@doris.apache.org mailing lists remain the primary venues for design discussions, vote threads, and release announcements, with a consistent flow of release votes (4.0.4, 4.0.5, 4.1.0-rc01) and DISCUSS threads on the streaming, AI/vector, and cloud workstreams. GitHub activity — issues, PR review, and discussions — continues to be the most active surface day-to-day, which is typical for the project given its global, multi-region contributor base. On the regional balance front, contributor activity is still concentrated in the Asia–Pacific region, with growing but still under-represented participation from contributors in Europe and North America. The community has been actively addressing this through English-language design docs, translated user documentation, and meetups and conference talks at international venues; we'd welcome guidance from the broader Apache community on how to further grow the non-APAC contributor base. We are slightly under-staffed in two specific areas where help would be especially welcome: - Documentation and translation — particularly keeping the English docs in sync with new features such as streaming jobs, Iceberg MERGE INTO, ANN/AI features, and the new authentication framework. - UI / Console design — front-end and design contributors remain rare relative to engine contributors, and we would appreciate suggestions from the board or others reading this report on how to reach a wider group of UI/UX designers willing to contribute to an OSS analytical database. No PMC- or board-level concerns to escalate this quarter; community discussions have been civil, decisions have followed The Apache Way, and release cadence and review throughput are both healthy. ----------------------------------------- Attachment T: Report from the Apache Drill Project [Charles Givre] ----------------------------------------- Attachment U: Report from the Apache Druid Project [Abhishek Agarwal] ----------------------------------------- Attachment V: Report from the Apache Empire-db Project [Rainer Döbele] ## Description: Empire-db is a lightweight relational database access library dealing with all aspects of storing, manipulating, retrieving and modelling data in relational database management systems (RDBMS). As an alternative to traditional OR-Mapping solutions, it provides an SQL centric, no-compromise approach that uses a Java-Object-Model rather than Mapping Files or Annotations. ## Project Status: Current project status: Ongoing with moderate activity Issues for the board: None ## Membership Data: Apache Empire-db was founded 2012-01-24 (14 years ago) There are currently 11 committers and 10 PMC members in this project. The Committer-to-PMC ratio is roughly 6:5. Community changes, past quarter: - Ralf Eichinger was added to the PMC on 2026-04-16 - Sascha Geissler was added to the PMC on 2026-04-16 - No new committers. Last addition was Sascha Geissler on 2025-12-02. ## Project Activity: Latest release is empire-db-3.4.0 released on 2025-10-22. We are happy to announce that the Empire-db PMC has voted to promote our two latest committers Ralf and Sascha into the PMC due to their contributions. Besides that work on the project consisted mainly of bugfixes and small improvements. ## Community Health: Our community is still alive and healthy. 6 JIRA tickets were opened and 1 closed in the past quarter. Also we have received a request for JIRA access and a pull request from a previously unknown user. ----------------------------------------- Attachment W: Report from the Apache EventMesh Project [Eason Chen] ## Description: The mission of Apache EventMesh is the creation and maintenance of software related to a fully serverless platform used to build distributed event-driven applications ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache EventMesh was founded 2023-03-22 (3 years ago) There are currently 54 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 7:2. Community changes, past quarter: - No new PMC members. Last addition was Jianbo Liu on 2024-01-05. - No new committers. Last addition was Zikang Chen on 2025-01-28. ## Project Activity: Add A2A Agent Card Registry to EventMesh pr has been merged. Refactor/unified runtime pipeline and protocol processors pr is under reviewing. Answering questions & issues from some users. New user: Liaoning Boyu Technology Co., Ltd. ## Community Health: The new features were under designing or developing, so the commits and PR activity seems decrease. Contributors increased slightly compared to the previous quarter. Overall community health is good. ----------------------------------------- Attachment X: Report from the Apache FreeMarker Project [Dániel Dékány] ## Description: Apache FreeMarker is a template engine, i.e. a generic tool to generate text output based on templates. Apache FreeMarker is implemented in Java as a class library for programmers. FreeMarker 2 (the current stable line) produces releases since 2002. The FreeMarker project has joined the ASF in 2015, and graduated from the Incubator in early 2018. ## Issues: There are no issues requiring board attention at this time. ## Activity: Activity was very low in recent months. ## Health report: Activity was very low in recent months, though such periods are not unusual for this project. User questions and new Jira issues are still being answered. Most PR-s slowly but eventually getting reviewed and merged. Infrastructure maintenance is done (such as recent migration of try.freemarker.apache.org virual machine). The next goal is to make the next minor release, regardless of how few changes have accumulated given how long it has been since the last release. Bigger task still unfinished in 2.x line is the java.time support (FREEMARKER-35). The even longer term goal is continuing the ongoing development on the 3.0 branch, so that the project can innovate, and the code base can become more modern and attractive for new committers. ## PMC changes: - Currently 9 PMC members. - Last added on 2025-01-01 ## Committer base changes: - Currently 12 committers. - Last added (non-PMC): Siegfried Goeschl on 2020-01-07 ## Releases: - 2.3.34 was released on 2024-12-22 ----------------------------------------- Attachment Y: Report from the Apache Geode Project [Mark Bretl] ## Description: The mission of Apache Geode is the creation and maintenance of software related to a data management platform that provides real-time, consistent access to data-intensive applications throughout widely distributed cloud architectures. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Geode was founded 2016-11-15 (9 years ago) There are currently 126 committers and 34 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - Leon Finker was added to the PMC on 2026-04-22 - Yuwei Chang was added as committer on 2026-04-28 - Bryan Behrenshausen was added as committer on 2026-04-08 ## Project Activity: In the past quarter, the community released maintenance releases for both our main development and support versions, 2.0.1 and 1.15.3 respectively. There are new discussions about updating Geode documentation, including the project website. ## Community Health: Overall community health is good with releases and community involvement on mailing lists. There is a decrease in many of the statistics as the previous time period included a major release and long term roadmap discussions, we expect some more involvement as the community is targeting modernization efforts of the Gedoe site. ----------------------------------------- Attachment Z: Report from the Apache Geronimo Project [Jean-Louis Monteiro] ----------------------------------------- Attachment AA: Report from the Apache Gluten Project [Weiting Chen] ## Description: The mission of Apache Gluten is the creation and maintenance of software related to software related to a pluggable middleware that enables native, vectorized execution engines to accelerate Apache SparkSQL workloads; ## Project Status: Current project status: Ongoing. Issues for the board: None. ## Membership Data: Apache Gluten was founded 2026-02-18 (3 months ago) There are currently 45 committers and 28 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members (project graduated recently). - Ankita Victor was added as committer on 2026-04-16 ## Project Activity: Release * Latest official release listed publicly: v1.6.0 (Mar 10, 2026) Development activity snapshot in the past one month * 27 active pull requests; 10 active issues * 10 merged pull requests; 17 opened pull requests * 7 new issues; 3 closed issues Notable merged PRs * Delta/VL compatibility fixes and Spark4 enablement work were merged * Infra/CI and build-related changes landed ## Community Health: Public signals available without ASF login: * GitHub PR and issue activity remained active in the most recent Pulse snapshot (numbers above), including 10 unresolved conversations across issues/PRs (indicating ongoing review/discussion load) * Repo scale indicators (public): ~1.6k stars, ~600 forks ----------------------------------------- Attachment AB: Report from the Apache Grails Project [James Fredley] ## Description: The mission of Apache Grails is the creation and maintenance of software related to the development of a powerful Groovy-based web application framework for the JVM built on top of Spring Boot ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Grails was founded 2025-09-23 (7 months ago) There are currently 17 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 9:7. Community changes, past quarter: - No new PMC members. Last addition was Thomas Rasmussen on 2026-01-19. - Mihael Koep was added as committer on 2026-04-28 ## Project Activity: CORE-8.0.0-M1 was released on 2026-05-07. ACTIONS-1.0.2 was released on 2026-05-03. CORE-7.0.11 was released on 2026-05-03. CORE-7.1.1 was released on 2026-05-03. GRAILS-PUBLISH-0.0.5 was released on 2026-05-03. GRAILS-PUBLISH-1.0.0-M1 was released on 2026-05-03. SPRING-SECURITY-7.0.2 was released on 2026-05-03. CORE-7.1.0 was released on 2026-04-15. CORE-7.0.10 was released on 2026-04-04. CORE-7.1.0-RC1 was released on 2026-04-04. CORE-7.0.9 was released on 2026-03-16. CORE-7.0.8 was released on 2026-03-08. SPRING-SECURITY-7.0.1 was released on 2026-02-15. QUARTZ-4.0.1 was released on 2026-02-14. REDIS-5.0.1 was released on 2026-02-14. ## Community Health: The community is healthier than it's been in several years. There's a lot of new contributors including a number that began contributing in order to attempt to participate in the Google Summer of Code. The mailing traffic is up quite significantly on the dev and users mailing list as we're working towards Grails version 8, which is the next major version. ----------------------------------------- Attachment AC: Report from the Apache Groovy Project [Paul King] ## Description: Apache Groovy is responsible for the evolution and maintenance of the Groovy programming language ## Project Status: Current project status: Ongoing with moderate activity Issues for the board: None ## Membership Data: Apache Groovy was founded 2015-11-18 (10 years ago) There are currently 24 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Jonny Carter on 2025-12-02. - No new committers. Last addition was Carl B. Marcum on 2025-12-01. ## Project Activity: Recent releases: 4.0.32 was released on 2026-05-07. 5.0.6 was released on 2026-05-07. 6.0.0-alpha-1 was released on 2026-05-07. 4.0.31 was released on 2026-03-29. 5.0.5 was released on 2026-03-29. ## Community Health: There was an uptick in community activity in the last quarter. 146 JIRA tickets opened and 185 closed in the past quarter. Community Health Score (Chi): 9.60 (Super Healthy) We just released our first milestone version of Groovy 6. We are excited by the many features this new version of Groovy offers. It includes features that AI agents have requested from a programming language to make Groovy a very efficient language to reason about once agents are trained on its latest features. We look forward to contributing to the Community over Code Glasgow conference in October. An excellent select of talks has been accepted for the Groovy Track covering Groovy, Geb and Grails among other topics in the broader Groovy ecosystem. ----------------------------------------- Attachment AD: Report from the Apache Hop Project [Hans Van Akelyen] ----------------------------------------- Attachment AE: Report from the Apache HTTP Server Project [Joe Orton] ## Description: The mission of HTTP Server is the creation and maintenance of software related to Apache Web Server (httpd) ## Project Status: Current project status: Ongoing, moderate activity Issues for the board: None ## Membership Data: Apache HTTP Server was founded 1995-02-27 (31 years ago) There are currently 126 committers and 55 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Vincent Deffontaines was added to the PMC on 2026-04-10 - No new committers. Last addition was Emmanuel Dreyfus on 2022-11-05. ## Project Activity: Like other high profile open source projects, we have seen an extraordinary surge in the number of security vulnerabilities being reported since February when the project last reported to the Board - unsurprisingly driven by LLM analysis. As in my previous report, it remains true that the majority of the incoming reports are true positives (i.e. valid vulnerabilities), though it's likely we're rejecting a somewhat higher percentage of the reports than previously. With several individuals reporting issue counts into double-digits, plus gaining access to some bulk analysis via the Alpha-Omega project, the backlog of (potential) vulnerabilities to process is growing faster than we can handle. Our security workflow and our people are struggling to cope. Only a small number of committers are active doing e-mail response, triage and patch review. Without a ticketing system, reports are likely to be missed, and our (labour intensive) workflow for handling fixes requires significant effort to address any single report. We're experimenting with using AI/LLM-based agent tools to handle incoming reports, and there is some streamlining we can do to the workflow. If there is good news in this report, it is that most of the LLM-reported issues are rated Low or Moderate severity. The project released 2.4.67 on May 4th, addressing eleven vulnerabilities - 1 rated Important severity, 2 rated Moderate and 8 rated Low. This is probably a record CVE count for any single release. The PMC voted to archive/retire the "libapreq2" library, which we took over from the Perl PMC but has had little interest/development from committers in recent years. Existing committer Vincent Deffontaines joined the PMC, and Giannis Christodoulou has also accepted an invite for both commit access and PMC membership. ## Community Health: Mailing lists and Bugzilla were very busy this quarter, which is partly due to the release activity. Rich Bowen has done an incredible job working through the entire backlog of documentation bugs, with a swathe of updates across both the web site and the httpd manual. Significantly more Bugzilla bugs closed in a quarter than were opened, which I can't remember being true at any time during my tenure as Chair. ----------------------------------------- Attachment AF: Report from the Apache HttpComponents Project [Michael Osipov] ## Description: The mission of HttpComponents is the creation and maintenance of software related to Java toolset of low level HTTP components ## Project Status - There are no issues requiring board attention at this time. ## Membership Data: Apache HttpComponents was founded 2007-11-14 (18 years ago) There are currently 20 committers and 9 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - No new PMC members. Last addition was Arturo Bernal on 2023-10-27. - No new committers. Last addition was Arturo Bernal on 2023-06-20. ## Project Activity: - Development on master is 5.7 for Client and 5.5 for Core ## Community Health: - Overall the project remains active. Issues and dicussions are resolved in time. ## Releases: - HttpClient 5.6.1 GA: 2026-04-21 - HttpCore 5.5-alpha1: 2026-03-26 - HttpCore 5.4.2 GA: 2026-03-06 ----------------------------------------- Attachment AG: Report from the Apache Ignite Project [Dmitry Pavlov] ## Description: The mission of Ignite project is the creation and maintenance of software related to high-performance distributed database engine providing in-memory and persistent data caching, partitioning, processing, and querying components. ## Project Status: Current project status: Ongoing Issues for the board: none. ## Membership Data: Apache Ignite was founded 2015-08-19 (11 years ago) There are currently 80 committers and 42 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - Evgeny Stanilovsky was added to the PMC on 2026-03-07 - No new committers. Last addition was Stanislav Lukyanov on 2025-11-17. ## Project Activity: Ignite 2.x: - 2.18.0 was released on 2026-04-23 with major SQL/Calcite, MultiDC, observability, persistence/snapshot, CDC, and client-tooling improvements. - Continued internal modernization of messaging infrastructure for network modules along with multiple stability fixes. - CI migration to JDK 17 with flaky-test reduction, dependency updates, and documentation refreshes. Ignite 3.x: - Continued work on transaction reliability, replication, Raft/storage stability, and SQL/table-layer improvements. - Client/API improvements delivered better partition awareness, protocol fixes, and operational tooling enhancements. - Additional metrics, REST/CLI improvements, packaging fixes, and documentation updates were completed. ## Community Health: - Mailing-list activity increased across all lists. - dev@ traffic doubled, driven by the 2.18.0 release, JDK 17 migration, and IgniteClassPath/deployment-modernization discussions. - issues@ increased by 16%, notifications@ by 18%. - user@ increased by 60% with discussions focused on operational stability, production diagnostics, and dependency/security guidance for Ignite 2. ----------------------------------------- Attachment AH: Report from the Apache Impala Project [Zoltán Borók-Nagy] ## Description: The mission of Apache Impala is the creation and maintenance of software related to a high-performance distributed SQL engine ## Project Status: Current project status: Ongoing with high activity Issues for the board: None ## Membership Data: Apache Impala was founded 2017-11-15 (8 years ago) There are currently 72 committers and 41 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Jason Fehr on 2025-09-10. - No new committers. Last addition was Noémi Pap-Takács on 2025-03-12. ## Project Activity: - Integration with Apache Calcite - Apache Iceberg V3 support - Iceberg metadata handling optimizations - Event processing improvements - Lineage improvements - Event processor improvements - Parquet reader enhancements - Observability improvements - OpenTelemetry integration ## Community Health: reviews@ is the most reliable metric of Impala community activity level. There were 2888 emails to that list in March, Apry, and May (until 12nd) ----------------------------------------- Attachment AI: Report from the Apache Incubator Project [Justin Mclean] # Incubator PMC report for May 2026 The Apache Incubator is the entry path into the ASF for projects and codebases wishing to become part of the Foundation's efforts. There are currently 28 podlings under incubation. In April, the Incubator made 6 releases, and some release votes are currently underway. There were two additions and no removals to IPMC membership. Mailing list discussion in April focused primarily on release voting activity. There was also a discussion about using MCP-based tooling with publicly available data to generate Incubator insights, which sparked interest on the mailing list. This tooling was subsequently used, with human oversight, to help produce this report. A new incubation proposal for PIC Standard was discussed. A graduation discussion for Apache Livy has started. Caldera has shown very limited engagement with ASF since entering incubation. Project communication has not been taking place on the mailing lists, and initial setup tasks, including ICLAs, accounts, and SGA progress, have not been progressing visibly. The IPMC raised these concerns with the project, and the podling has confirmed it will change course to address them and is making progress. Casbin is a new podling (entered February 2026) submitting its first report. Development activity still appears to be primarily occurring outside ASF infrastructure, and project discussions are taking place on Discord and GitHub Discussions rather than on the mailing lists. The IPMC will monitor this. OpenServerless has been incubating for nearly two years and has not yet released an ASF release. Mailing list activity is almost entirely automated GitHub messages. No new committers or PPMC members have been elected since August 2024, and a private message sent to the podling about one month ago has not received a response. Mentor comments in the most recent reports and on the general list directly reflect these concerns. The IPMC has raised the question of whether to initiate a discussion about retirement. OpenServerless has started to move towards marking a release. OzHera has not made an ASF release in over a year despite ongoing development activity. The project has been asked to outline the current status of release preparation, what is blocking the next release, and to address low mentor engagement across recent reporting periods. PouchDB has been in incubation for 12 months with no ASF release. The project website at pouchdb.apache.org needs some work (which looks to have been done), and the previous project site at pouchdb.com still exists where it shouldn't. The IPMC raised these issues with the project's mentors, and the project is working to address them. The IPMC continues to monitor long-running podlings and will follow up on any release or community concerns as needed. In particular, Toree has been incubating since December 2015. The project is actively working through release candidate iterations and plans to push for graduation once the release completes. Upon submission, only Texera lacked a sign-off. ## Community ### New IPMC members: - Jark Wu - Russell Spitzer ### People who left the IPMC: - No one ## New Podlings - None ## Podlings that failed to report, expected next month - Pony Mail ## Graduations - None The board has motions for the following: - None ## Releases The following releases entered distribution during the month of April: - Cloudberry 2.1.0 - Fluss-rust 0.1.0 - Hamilton 1.90.0 - Iggy 0.8.0 - KIE 10.2.0   - ResilientDB 1.12.0 ## IP Clearance - None ## Legal / Trademarks N/A ## Infrastructure N/A ## Table of Contents [Burr](#burr) [Caldera](#caldera) [Casbin](#casbin) [Cloudberry](#cloudberry) [Fesod](#fesod) [GeaFlow](#geaflow) [GraphAr](#graphar) [Hamilton](#hamilton) [Seata](#seata) [Texera](#texera) [Toree](#toree) [XTable](#xtable) -------------------- ## Burr Burr is a lightweight in-process python framework that standardizes the expression and execution of state machines as action-driven graphs, while making graph execution easily observable. It is particularly suited for AI agent workflows, simulations, and other dynamic systems, and comes with a self-hostable observability UI that integrates with OpenTelemetry. Burr has been incubating since 2025-05-24. ### Three most important unfinished issues to address before graduating: 1. Complete second Apache release (0.42.0-incubating) — vote on incubator general currently in progress. 2. Diversify reviewer base — reviewer diversity (effective # 1.87) is concentrated; need more independent reviewers for PRs 3. Grow independent committer base — currently 3 active committers with commit activity (skrawcz, ebenizzy, and community contributors); need to identify and elect new committers from active contributors ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? • 7 new contributors in the last 3 months, 14 over 6 months • 12 unique committers active in the 3-month window • 10 unique PR authors and 6 unique reviewers (sampled) • dev@ mailing list has 12 unique posters • Active participation in release votes from mentors (Jernej Frank, PJ Fanning, Jarek Potiuk) and community members • André Ahlert added as collaborator and leading UI contributions (16 commits since Jan 2026) ### How has the project developed since the last report? • First official Apache release (0.41.0-incubating) completed and published to dist.apache.org (~January 2026) • 0.42.0-incubating RC3 vote in progress (started April 26); RC1 and RC2 received constructive feedback on licensing which was addressed • New features: AWS Bedrock integration (#677), cloud-native AWS deployment example (#666), ecosystem page for website (#661), flexible_api decorator for mypy compatibility (#683), async persister improvements (#681), graceful stream shutdown (#680) • CI/infrastructure improvements: repo governance workflows, release validation pipeline, automated artifact verification • 34 issues closed since January 2026; 58 commits in 3-month window • Median PR time-to-merge: 2.4 days ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2026-01-25 ### When were the last committers or PPMC members elected? No new committers or PPMC members have been elected since the initial roster was established (last LDAP modification: 2025-10-22). One active contributor André Ahlert is a candidate for election. ### Have your mentors been helpful and responsive? No answer. ### Is the PPMC managing the podling's brand / trademarks? Not aware of any issues. ### Signed-off-by: - [ ] (burr) Kevin Ratnasekera Comments: - [ ] (burr) Ayush Saxena Comments: - [X] (burr) PJ Fanning Comments: Need to look at adding extra committers from the active contributors. - [ ] (burr) Jarek Potiuk Comments: ### IPMC/Shepherd notes: -------------------- ## Caldera Caldera provides a modular platform for modeling, scripting, and executing adversary behavior. It allows users to construct emulation plans, provides agents for communicating with the command and control server, and enables users to evaluate security detections in a structured, scalable, and repeatable way. With the use of plug- ins and community-contributed features, Caldera supports a range of use cases including adversary emulation, purple teaming, detection engineering, and continuous security validation. Using Caldera, defenders can emulate known threat actor behavior and perform other red team activity to evaluate their organization’s defensive capabilities, test analytics, and find detection gaps. As a modular tool based on the MITRE ATT&CK framework, Caldera is designed to be extensible, intelligence-driven, and automation-friendly. Caldera has been incubating since 2025-12-19. ### Three most important unfinished issues to address before graduating: 1. Caldera GitHub repository needs to be transferred 2. Apache Caldera website needs to be stood up 3. Community growth ### Are there any issues that the IPMC or ASF Board need to be aware of? - Awaiting response from Apache infra team for GitHub repository transfer ### How has the community developed since the last report? - Caldera Discord community growing ~500 users - Caldera GitHub community actively submitting PRs - GitHub stars reached 6.9k ### How has the project developed since the last report? - Preparing for GitHub repository transfer to ASF - Approved 5 PRs from contributors - Caldera WIKI created. Link: cwiki.apache.org/confluence/display/CALDERA ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [X] Other: Awaiting repository transferring (May 20th). ### Date of last release: N/A ### When were the last committers or PPMC members elected? at founding/incubation ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? No known brand or naming issues. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-248 approved. ### Signed-off-by: - [ ] (caldera) Kevin Ratnasekera Comments: - [X] (caldera) Francis Chuang Comments: There were some delays with getting the project into the incubator, but the PPMC has made significant progress in the last few months to get the ball rolling. - [X] (caldera) PJ Fanning Comments: There was talk of adding some new named PPMC members but the discussion has not been made official on the private list. - [ ] (caldera) Gordon King Comments: ### IPMC/Shepherd notes: -------------------- ## Casbin Casbin is a powerful, efficient open-source access control framework offering a unified, model-driven authorization approach. Based on the PERM (Policy, Effect, Request, Matchers) metamodel and its domain-specific language (DSL), Casbin seamlessly integrates ACL, RBAC, and ABAC models to enable flexible and fine-grained policy management. It delivers high-performance access control enforcement and supports a comprehensive multi-language ecosystem including Go, Java, Node.js, Python, .NET, C++, and Rust. Apache Software Foundation incubation will establish Casbin as a community-driven, standardized authorization solution. Casbin has been incubating since 2026-02-07. ### Three most important unfinished issues to address before graduating: - Establish a clear release process aligned with ASF guidelines and perform the first official Apache release. - Grow the community by onboarding new contributors from diverse organizations and transitioning discussions to Apache mailing lists. - Complete the formal transfer of domains and trademarks to the ASF. ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? - Officially announced Casbin's acceptance into the Apache Incubator and published the news via project blogs and community channels - Raised community activity: a new group of developers have joined the discussions on Discord and GitHub Discussions - Maintained steady growth in GitHub stars (the main repository increased from 19.4k to 20.1k) - During the incubation period, the download volume of packages across all language versions has kept rising, with the overall ecological adoption growing steadily - dev@casbin.apache.org saw 44 emails (mostly Dependabot bot notifications), including a community discussion proposal, with new subscribers joining. ### How has the project developed since the last report? - This is the first official monthly report for Casbin following its admission to the Apache Incubator - Added standardized configuration files and optimized the project's overall configuration management system - Implemented ASF compliance requirements: added the official .asf.yaml configuration file and Apache disclaimer file to ensure the project is fully compliant with the foundation's norms - Completed the addition of standard Apache License 2.0 headers to the entire codebase and initiated the preliminary intellectual property transfer process to the ASF - A total of 30 PRs merged and 40 issues closed during the incubation period ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: No apache release yet. ### When were the last committers or PPMC members elected? 2026-02-07 ### Have your mentors been helpful and responsive? Yes, very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? Name is approved: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-251 ### Signed-off-by: - [ ] (casbin) Hao Ding Comments: - [ ] (casbin) Huajie Wang Comments: - [ ] (casbin) Hulk Lin Comments: - [ ] (casbin) Jerry Shao Comments: - [X] (casbin) Zili Chen Comments: ### IPMC/Shepherd notes: -------------------- ## Cloudberry Cloudberry is an advanced and mature open-source Massively Parallel Processing (MPP) database, derived from the open-source version of Pivotal Greenplum Database®️ but built on a more modern PostgreSQL 14 kernel, whereas Greenplum is based on PostgreSQL 12. This upgrade brings enhanced enterprise capabilities, making Cloudberry well-suited for data warehousing, large-scale analytics, and AI/ML workloads. Cloudberry has been incubating since 2024-10-11. ### Three most important unfinished issues to address before graduating: 1. Grow the contributor and community to ensure long-term sustainability. 2. Publish a few more Apache releases following the ASF release processes. ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? - The community continued the Apache Cloudberry bi-weekly community meeting, holding five public meetings from February to April 2026. These meetings covered release coordination, kernel upgrades, ecosystem projects, testing strategy, events, and open community topics. - New Committers: Xiaoyu Liu (@misterRaindrop), Nikolay Antonov (@ostinru), Robert Mu (@robertmu) - New PPMC Member: Leonid Borchuk - Community channels: - Created a new Slack workspace and a new Discord server after the previous Slack workspace became unavailable. - Updated the website and planned updates across related repositories to point users to the current communication channels. - Governance and community process: - Started discussion on an AI conduct policy to guide responsible use of LLM tools while following ASF copyright and attribution expectations. - Added a website page documenting how to invite new PPMC members. - Events and outreach: - Community Over Code Asia 2026: around 11 Cloudberry-related proposals, now waiting for the review results. Plan to organize one in-person community gathering in Beijing during the conference. - A Cloudberry meetup was organized in Moscow, with public recordings and a Russian Habr article bringing more user feedback to the community. - Two community members were confirmed as PGConf.dev 2026 speakers. - New contributors appeared in community discussions and PRs, including contributions around Cloudberry Backup, PXF, and core repository features. ### How has the project developed since the last report? - Released Apache Cloudberry (Incubating) 2.1.0 in April 2026, the project's second Apache release after entering the ASF Incubator. Convenience RPM/DEB packages and binary packages were provided for the first time. Manual packages were made for 2.1.0, and automation is being considered for 2.2.0. - PostgreSQL kernel upgrade: - Started the PostgreSQL 14.x minor-version upgrade work for the 2.x release branch. The branch progressed from PostgreSQL 14.4 through 14.8, with later 14.x updates being tracked in the project Kanban. - Continued the PostgreSQL 16 kernel upgrade on the work development branch. This work is expected to be completed by the end of Q2 2026. - Fixed PostgreSQL upstream CVEs and security-related patches, including libpq SSL/GSS negotiation error handling. - Core project improvements: - Merged the diskquota extension into the main repository. - Added the gp_stats_collector extension, improving observability and laying groundwork for dashboard related work. - Added AQUMV exact-match support for multi-table JOIN queries. - Started discussion on an Iceberg subsystem for `datalake_fdw`. - CI, testing, and platform support: - Added Ubuntu 24.04 Docker image and test matrix support. - Continued Rocky Linux 10 support work, with initial build docker images. The related test matrix support is to be added. - Started discussion on rethinking the testing strategy for better test efficiency and coverage. - Upgraded Go to 1.24 in Cloudberry development images and related ecosystem repositories. Newer Go version support is in the discussion. - Started adding Behave tests for gpMgmt tools (WIP). - Ecosystem and sub-repositories: - `cloudberry-pxf`: - Started a roadmap discussion for the PXF project. - Released 2.1.0, the first Apache release for PXF. - Renamed Java packages from `org.greenplum` to `org.apache.cloudberry` and updated ASF compliance files. - Added Java 17 support and Rocky Linux 9 CI support. - Removed `gradle-wrapper.jar` from source release artifacts and download/verify it during build for ASF license compliance. - Added or improved JDBC tests using Testcontainers for ClickHouse, MS SQL, and Oracle. - Upgraded dependencies including Apache AVRO, Apache ORC, Parquet, and HBase related components, and discussed Java 21 support. - `cloudberry-backup`: - Released 2.1.0, the first Apache release for gpbackup. - Completed migration work from legacy Concourse CI to GitHub Actions. - Added ASF release script support and Cloudberry 2.1 compatibility. - Started a roadmap discussion for the backup project. - Merged gpbackman-related backup management work. The Prometheus exporter for the gpbackup history database work is in the review process. - `cloudberry-go-libs`: - Tracked a security issue and dependency update needed by related backup tooling. - Apache MADlib: - Continued collaboration with Apache MADlib to add Apache Cloudberry support upstream, with community discussion ongoing. See: https://s.apache.org/bsu9m - Next release: Started early discussion for Apache Cloudberry 2.2.0, including release manager, release process documentation, packaging automation, and testing strategy. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: - April 14, 2026 - Apache Cloudberry (Incubating) 2.1.0 ### When were the last committers or PPMC members elected? - March 24, 2026 - Xiaoyu Liu (@misterRaindrop), Nikolay Antonov (@ostinru), Robert Mu (@robertmu) were announced as new committers. - April 07, 2026 - Leonid Borchuk was announced as a new PPMC member. ### Have your mentors been helpful and responsive? Yes. ### Is the PPMC managing the podling's brand / trademarks? Yes. ### Signed-off-by: - [ ] (cloudberry) Roman Shaposhnik Comments: - [ ] (cloudberry) Willem Ning Jiang Comments: - [X] (cloudberry) Kent Yao Comments: ### IPMC/Shepherd notes: -------------------- ## Fesod Fesod is a high-performance and memory-efficient Java library for reading and writing Excel files, designed to simplify development and ensure reliability. Fesod has been incubating since 2025-09-17. ### Three most important unfinished issues to address before graduating: 1. Ensure that the website and codebase are fully compliant with ASF policies, 2. Add more core contributors. 3. Get more focused on building community. ### Are there any issues that the IPMC or ASF Board need to be aware of? N/A ### How has the community developed since the last report? 1. We discussed and voted to approve two new committers. 2. As the community has begun to become more organized, the number of contributors is growing steadily. ### How has the project developed since the last report? 1. we discussed some future core roadmap plans on the mailing list; 2. We plan to release the second version of the incubator around June; 3. In addition to developing new features, we are also working on enhancing the project's foundational tools. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2026-02-11 ### When were the last committers or PPMC members elected? 2026-04-22 ### Have your mentors been helpful and responsive? Yes. We truly thanks our mentors' help in daily guidance and reminders. ### Is the PPMC managing the podling's brand / trademarks? Yes. https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-246 ### Signed-off-by: - [X] (fesod) tison Comments: - [ ] (fesod) Dave Fisher Comments: - [ ] (fesod) Huajie Wang Comments: - [X] (fesod) PJ Fanning Comments: ### IPMC/Shepherd notes: -------------------- ## GeaFlow GeaFlow is a streaming graph computing engine for distributed large-scale real-time graph storage and analysis. It supports trillion-level graph storage, hybrid graph and table processing, real-time/offline graph computing, and interactive graph analysis. Currently, the community is actively advancing the development of Graph Memory, aiming to serve as the underlying infrastructure for Agent Memory. GeaFlow has been incubating since 2025-06-06. ### Three most important unfinished issues to address before graduating: 1.Cultivate a more diverse community by engaging contributors and committers from varied organizations and global regions. 2.Implement predictable release cycles and maintain high project stability to encourage broad participation and adoption. ### Are there any issues that the IPMC or ASF Board need to be aware of? No ### How has the community developed since the last report? The GeaFlow community has maintained its core contributor base over the past month, with existing contributors continuing to drive development. The community has remained active with ongoing contributions including new features, optimizations, and bugfix. Additionally, several PRs are currently under review. Furthermore, multiple community contributors are actively participating in CoC Asia 26, which will be held in Beijing, China, and have prepared multiple proposals for the associated Incubator, Streaming, and Data+AI tracks. ### How has the project developed since the last report? Over the past month, the GeaFlow project has continued its progress with a focus on code robustness, dependency management, and community facilitation. Key developments include: - Introduced the CONTRIBUTING.md file to outline contribution guidelines, facilitating easier onboarding for new developers (#765). - Enhanced code stability by adding checks for empty search results to prevent array out of bounds errors (#769) and handling null/empty inputs in average methods (#760). - Optimized code quality by defining the BYTES_PER_KB constant for consistency (#770), replacing raw type usage with type-safe methods (#766), and excluding conflicting lucene-core dependencies (#778). - Improved CI infrastructure by formatting build and test commands for better readability (#763). - New pull requests were opened targeting production GCN inference pipelines, hot-reload mechanisms, and vector implementation, indicating active development in AI capabilities and architecture optimization. These updates demonstrate continued advancement in codebase health, project infrastructure stability, and the expansion of Graph+AI features. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: The last version was released on November 19, 2025. ### When were the last committers or PPMC members elected? The last committers were elected on January 4, 2026. ### Have your mentors been helpful and responsive? Yes, we have received helpful guidance. ### Is the PPMC managing the podling's brand / trademarks? N/A. ### Signed-off-by: - [ ] (geaflow) Willem Ning Jiang Comments: - [X] (geaflow) Xin Wang Comments: - [ ] (geaflow) Jingsong Lee Comments: - [ ] (geaflow) Paul Klingelhuber Comments: - [X] (geaflow) Justin Mclean Comments: ### IPMC/Shepherd notes: -------------------- ## GraphAr GraphAr is an open-source and language-independent data file format designed for efficient graph data storage and retrieval. GraphAr has been incubating since 2024-03-25. ### Three most important unfinished issues to address before graduating: 1.Attract more committers, contributors, and users to grow the community. 2. Release more versions compliant with ASF standards. ### Are there any issues that the IPMC or ASF Board need to be aware of? None. ### How has the community developed since the last report? 1. A new contributors completed PR merge 2. Add two new Committers ### How has the project developed since the last report? 1. Merged 37 PRs since the last report. 2. Rust module: added GraphInfo support, enabled Rust build on macOS and updated Arrow linking. 3. C++ library code quality improvements: added clang-tidy/clang-format integration, enforced strongly-typed enums (enum class), enabled -Wall -Werror -Wextra compilation flags, removed unused variables and headers, and used std::move to reduce copies. 4. Refactored CMake build system: restructured CMake files into subdirectories, added ccache support for faster builds, added pre-commit hooks and commit message validation. 5. CI/CD improvements: enabled macOS CI, replaced make with ninja, added ccache support, validated PR titles, and switched to ubuntu-slim runners. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2025-08-29 ### When were the last committers or PPMC members elected? 2026-04-22 ### Have your mentors been helpful and responsive? The mentors are very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? There are no known brand and naming issues. ### Signed-off-by: - [ ] (graphar) Calvin Kirs Comments: - [X] (graphar) tison Comments: - [ ] (graphar) Xiaoqiao He Comments: - [ ] (graphar) Yu Li Comments: ### IPMC/Shepherd notes: [PJF] Maybe time to start thinking about Graduation (incubating for 2 years). Dev list mail traffic is very low but it does seem like podling is fairly active generally. -------------------- ## Hamilton Hamilton is a lightweight in-process framework to define, execute, and observe directed acyclic graphs (DAGs) that express data transformations. In Hamilton, one can express complex DAGs of transformations, e.g. from dataframe transformations (using pandas, polars, PySpark), machine learning pipelines, through to regular software engineering API request and LLM API based workflows. Observability hooks are built into the framework. The Hamilton UI is a self-hostable service to capture observability output from workflow runs. Hamilton has been incubating since 2025-04-12. ## Three most important unfinished issues to address before graduating: 1. **Grow reviewer/committer diversity** — Bus factor proxy is 2/3 (50%/75% of commits). Need to cultivate more regular reviewers beyond the core 2-3 maintainers. Reviewer diversity (effective #) is 1.68, which needs improvement. 2. **Establish a regular release cadence** — Two incubating releases to date (v1.89.0 in Oct 2025, v1.90.0 in Apr 2026). Need to demonstrate a sustainable, community-driven release process. 3. **Complete package rename from sf-hamilton to apache-hamilton** — Migration from the legacy `sf-hamilton` PyPI package to `apache-hamilton` is in progress (PR #1561). This is important for brand independence and Apache compliance. ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? - 8 new contributors in the last 3 months - 12 unique PR authors, 7 unique reviewers (sampled) in the 3-month window - 13 unique committers in the last 3 months - dev@ mailing list: 33 messages from 9 unique posters - Active community PRs from external contributors (ddtrace upgrade, datasaver fix, async typing fix, optional extractors feature, docs fixes) - PR activity strong: 97 opened / 72 merged in 3 months, median merge time 8 days ### How has the project developed since the last report? - **Released apache-hamilton v1.90.0-incubating** (April 2026) — second Apache release - Ongoing package rename from `sf-hamilton` to `apache-hamilton` across codebase, docs, and PyPI - Plugin upgrades (Datadog ddtrace 4.x migration) - Bug fixes for `from __future__ import annotations` compatibility - Typing improvements (fluent builder pattern with `Self`) - New feature: optional flag for `from_` data loaders - Dependency maintenance: security bumps for dompurify, django, follow-redirects, protobufjs, vite, lodash - Continued growth in external contributor PRs ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2026-04-25 ### When were the last committers or PPMC members elected? - At founding ### Have your mentors been helpful and responsive? I haven't asked yet, but better docs on docker build guidance would be appreciated. ### Is the PPMC managing the podling's brand / trademarks? Not that we're aware of. ### Signed-off-by: - [ ] (hamilton) Kevin Ratnasekera Comments: - [ ] (hamilton) Ayush Saxena Comments: - [X] (hamilton) PJ Fanning Comments: Need to look at adding extra committers from the active contributors. - [ ] (hamilton) Jarek Potiuk Comments: ### IPMC/Shepherd notes: -------------------- ## Seata Seata(Simple Extensible Autonomous Transaction Architecture)is an easy-to- use and high-performance distributed transaction solution, used to solve the data consistency problem. Seata has been incubating since 2023-10-29. ### Three most important unfinished issues to address before graduating: 1. Complete the transfer of Seata's existing trademarks to ASF. We have completed the signing of the Trademark Transfer Consent and POA documents and are currently awaiting further response from the ASF counsel team. ### Are there any issues that the IPMC or ASF Board need to be aware of? No issues at the moment. ### How has the community developed since the last report? 1. 32 new code contributors have joined the community (681 contributors in total) 2. 1 new committers and 2 new PPMC members were elected. 3. We have submitted proposals for 2 GSoC projects and submitted 3 topic proposals for Community over Code Asia. ### How has the project developed since the last report? 1. Since the last report, we have merged 77 PRs, primarily including several new architectural evolution features. 2. Since the last report, we have published two ASF releases: seata-2.6.0 and seata-go 2.1.0. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2026-03-12 ### When were the last committers or PPMC members elected? 2026-04-30 ### Have your mentors been helpful and responsive? Our mentors have been very helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? No Trademark issues. ### Signed-off-by: - [ ] (seata) Sheng Wu Comments: - [X] (seata) Justin Mclean Comments: - [X] (seata) Huxing Zhang Comments: The project is in good shape towards graduation after finishing the copyright transfer to ASF. - [ ] (seata) Heng Du Comments: - [X] (seata) Xin Wang Comments: ### IPMC/Shepherd notes: -------------------- ## Texera Texera is an open-source platform for human-AI collaborative data science using visual workflows. It enables human analysts to construct, execute, and refine data analysis tasks through an intuitive GUI, assisted by AI agents that understand natural-language instructions. Texera is well suited for a wide range of applications, including “AI for Science,” by making advanced AI and data science capabilities accessible to a broader community. It can run on a laptop for local use or be deployed in the cloud to support scalable processing of large datasets. Texera has been incubating since 2025-04-12. ### Three most important unfinished issues to address before graduating: 1. First incubating release (1.1.0-incubating): eight RCs cut in the window (rc2 through rc8); release vote / final still pending; 2. Increase community diversity, and need to identify and elect new committers from active contributors; 3. Trademark / brand assignment to ASF, need to confirm status with mentors. ### Are there any issues that the IPMC or ASF Board need to be aware of? N/A ### How has the community developed since the last report? - 8 new first-time contributors in the last 3 months: Anish Shivamurthy, Asish Kumar, Elliot Lin, Eugene Gu, Julie Cao, Kyle Dang, Nicole Ying, Prateek Ganigi. - 20 returning contributors. - 2 new promoted committers: Meng wang (mengw15) and Xuan Gu (xuang7). - dev@texera.apache.org list traffic: 262 messages, 17 unique posters across the window. - Active participation in release votes from mentors（PJ Fanning and Ian Maxon) and community members. ### How has the project developed since the last report? - In the past three months: 326 commits to main, 338 PRs merged (400 opened), 286 issues closed (351 opened). - We are actively preparing for the first apache release (1.1.0-incubating). A total of 8 RCs have been prepared and voted. We had major updates: - Fix many security issues reported by internal contributors and public users - Create a new service named "Result Service" to give fine grained access to computing units instead of allowing computing unit talk to database directly - Replace Ingress in the Kubernetes cluster with Envoy Gateway, which made computing units distributed across distant machines without the need to be part of one Kubernetes cluster - Improve dataset-upload experience by allowing resumable upload to support TB-scale data upload with connection disruptions - Improve the Github PR and issue management by adding automated tag and triage process - Built the first AI agent to help users create workflow without the need to manually drag and drop operators ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [X] Initial setup - [X] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: N/A ### When were the last committers or PPMC members elected? April 6 2026, a new committer: Meng Wang (mwang15). May 6 2026, a new committer: Xuan Gu (xuang7). ### Have your mentors been helpful and responsive? We learned so much from our mentors, more specifically: PJ: raised many PRs to address various security issues regarding version update, he also checked our first release and provide feedback very quickly in multiple rounds Ian: we worked actively with him on our first release, he constantly provide feedback in our process based on his previous experience including how to manage the security issues and prioritize them ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [ ] (texera) Cezar Andrei Comments: - [ ] (texera) Gordon King Comments: - [ ] (texera) PJ Fanning Comments: - [ ] (texera) Ian Maxon Comments: ### IPMC/Shepherd notes: -------------------- ## Toree Toree provides applications with a mechanism to interactively and remotely access Apache Spark. Toree has been incubating since 2015-12-02. ### Three most important unfinished issues to address before graduating: None ### Are there any issues that the IPMC or ASF Board need to be aware of? None, Nothing much of news from previous report ### How has the community developed since the last report? The community has focused heavily on getting Release 0.6.0 through the incubator review process. A significant portion of the recent mailing list discussions involved working through review feedback to ensure the project is fully compliant with graduation requirements, specifically around the proper attribution and packaging of legal files. The community wants to finalize and publish Release 0.6.0 and then push for graduation once the release process completes. ### How has the project developed since the last report? The project progressed through Release 0.6.0 preparation, moving from RC3 up to RC5 votes. The main technical work involved fixing the assembly process so the fat jar correctly includes all licenses and notices from bundled dependencies. We also had some minor repository maintenance, such as updating GitHub Actions for SBT setup. The upcoming release officially brings support for Scala 2.13 and Spark 3.4.4. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [ ] Community building - [X] Nearing graduation - [ ] Other: ### Date of last release: 2022-04-11 ### When were the last committers or PPMC members elected? - PJ Fanning was added to the PPMC on 2025-11-10 ### Have your mentors been helpful and responsive? Note applicable ### Is the PPMC managing the podling's brand / trademarks? No trademark issues ### IPMC/Shepherd notes: ### Signed-off-by: - [X] (toree) Luciano Resende Comments: The podling should push graduation after release is out - [ ] (toree) Ryan Blue Comments: - [ ] (toree) Weiwei Yang Comments: ### IPMC/Shepherd notes: -------------------- ## XTable XTable is an omni-directional converter for table formats that facilitates interoperability across data processing systems and query engines. XTable has been incubating since 2024-02-11. ### Three most important unfinished issues to address before graduating: 1. Cutting the next release (0.4.0-incubating) — RC1 is being prepared this week to re-establish a regular release cadence. 2. Landing the in-flight Delta Kernel APIs implementation (PR #801) and pluggable table format support to unlock new format integrations. 3. Continued community growth - broadening the contributor base beyond the current core set and graduating new committers/PPMC members. ### Are there any issues that the IPMC or ASF Board need to be aware of? No. ### How has the community developed since the last report? - 4 unique contributors made commits during this commits during this period (Alex R, Kevin Liu, Nicolas Paris, Rishi Reddy Bokka). - The community organizes a developer sync every 2 weeks and the last sync on 4th May we covered Delta Kernel, Hudi 1.x version upgrade, Paimon source completion, Parquet source completion and AI/MCP integration scope.[https://xtable.apache.org/community/sync/#typical-agenda] - First scoping discussions started for AI-related work for XTable (initial agent skills and an XTable MCP server). ### How has the project developed since the last report? - Parquet source matured significantly with expanded column stats support, schema conversion fixes, and snapshot sync stability for partitioned multi-commit scenarios. - Delta Kernel APIs implementation progressed and is pending merge (major milestone). - Hudi conversion hardened with fixes for batch INSERT_OVERWRITE replace-commits and empty earliest-commit-to-retain edge cases. - Delta conversion improved with stricter checkpoint CRC enforcement and NPE fixes for binary fields in nested schemas. - Iceberg nested comment handling fixed for qualified names. - Hudi version upgrade and pluggable table format support are in flight ahead of the next release. ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] Initial setup - [ ] Working towards first release - [X] Community building - [ ] Nearing graduation - [ ] Other: ### Date of last release: 2025-06-04 (0.3.0-incubating) ### When were the last committers or PPMC members elected? 2025-11-09 ### Have your mentors been helpful and responsive? Our mentors have been helpful and responsive. Following last report's feedback to speed up the release cadence, an RC1 is being cut this week to demonstrate momentum ### Is the PPMC managing the podling's brand / trademarks? No answer. ### Signed-off-by: - [X] (xtable) Jesús Camacho Rodríguez Comments: - [X] (xtable) Stamatis Zampetakis Comments: - [ ] (xtable) Jean-Baptiste Onofré Comments: ### IPMC/Shepherd notes: ----------------------------------------- Attachment AJ: Report from the Apache Johnzon Project [Jean-Louis Monteiro] ## Description: The mission of Johnzon is the creation and maintenance of software related to JSR-353 compliant JSON parsing; modules to help with JSR-353 as well as JSR-374 and JSR-367 ## Project Status: There are no issues requiring board attention. ## Project Activity: We've fixed a few bugs in the JSON-B area and updated dependencies, etc. In summary we cleaned up 11 tickets and rolled releases both for our active JavaEE 8 branch (Johnzon-1.3.0) and JakartaEE 10 (Johnzon-2.1.0) ## Community Health: Community is still very much composed of other Apache project leveraging Johnzon to deal with JSON. ## Membership Data: Apache Johnzon was founded 2016-04-20 (9 years ago) There are currently 9 committers and 6 PMC members in this project. The Committer-to-PMC ratio is 3:2. ## Community changes, past quarter: - No new PMC members. Last addition was Reinhard Sandtner on 2016-08-30. - No new committers. Last addition was Markus Jung on 2024-02-05. ## Releases: - 1.3.0: 2026-05-08 - 2.1.0: 2026-05-03 - 2.0.1: 2024-04-01 ----------------------------------------- Attachment AK: Report from the Apache Juneau Project [James Bognar] ## Description: The mission of Apache Juneau is the creation and maintenance of software related to a toolkit for marshalling POJOs to a wide variety of content types using a common framework, and for creating sophisticated self-documenting REST interfaces and microservices using VERY little code ## Project Status: Current project status: In active development Issues for the board: None ## Membership Data: Apache Juneau was founded 2017-10-17 (9 years ago) There are currently 13 committers and 12 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members. Last addition was Gary D. Gregory on 2023-04-02. - No new committers. Last addition was Aditya Kanthale on 2024-10-22. ## Project Activity: Currently working on a major release, V9.5. We hope to release this in the next 1-2 months. 9.2.0 was released on 2026-01-05. ## Community Health: Team is small but active. Email traffic decreased 58%, but this was primarily due to a reduction in automated notifications from dependency patches. ----------------------------------------- Attachment AL: Report from the Apache Kafka Project [Mickael Maison] ## Description: The mission of Kafka is the creation and maintenance of software related to Distributed publish-subscribe messaging system ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Kafka was founded 2012-11-21 (13 years ago) There are currently 71 committers and 44 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Christo Lolov was added to the PMC on 2026-02-23 - Kamal Chandraprakash was added to the PMC on 2026-02-22 - Lianet Magrans was added to the PMC on 2026-02-21 - Andrew Schofield was added to the PMC on 2026-02-23 - Viktor Somogyi-Vass was added to the PMC on 2026-02-23 - Kirk True was added as committer on 2026-03-24 - Sean Quah was added as committer on 2026-04-29 ## Project Activity: In the past quarter we released: - 4.0.2 was released on 2026-03-20 - 4.1.2 was released on 2026-03-17 - 3.9.2 was released on 2026-02-21 These are bugfix releases to address CVEs - 4.2.0 was released on 2026-02-16: This is a feature release that introduces significant improvements to all components: - Kafka Queues are now production ready - Major monitoring improvements - Auto join feature for KRaft voters - New Kafka Streams rebalance protocol - DLQ support for Kafka Streams We currently have 2 releases in progress: - 4.3.0 (RC1 vote in progress) - 4.2.1 (RC3 vote in progress) ## Community Health: The project activity on mailing lists, Jira and GitHub remains high and stable. ----------------------------------------- Attachment AM: Report from the Apache Knox Project [Larry McCay] ## Description: The mission of Knox is the creation and maintenance of software related to Simplify and normalize the deployment and implementation of secure Hadoop clusters ## Project Status: Current project status: Ongoing project with moderate activity and email traffic aligned with the status of a mature infra level project Issues for the board: none. ## Membership Data: Apache Knox was founded 2014-02-18 (12 years ago) There are currently 26 committers and 22 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members. Last addition was Tamás Marcinkovics on 2025-11-10. - No new committers. Last addition was Tamás Marcinkovics on 2025-10-17. ## Project Activity: * 2.1.0 was released on 2025-09-25 * 2.0.0 was released on 2023-02-27 ## Community Health: dev@knox.apache.org had a 87% increase in traffic in the past quarter (987 emails compared to 526) 71 JIRA tickets opened and 60 closed in the past quarter. Activity related to OAuth and Agentic Identity initiatives have been initiated with Delegated Authentication and RFC 8693 token exchanges. Moved to Java 17+ and deprecated Java 8 with 2.1.0 likely to be the last release that supports Java 8. Activity seems about normal with an uptick since the previous quarter which included holiday season which is normally slower. Health score seems skewed by obsolete doap file. This will be corrected. ----------------------------------------- Attachment AN: Report from the Apache Kylin Project [Yang Li] ## Description: The mission of Apache Kylin is the creation and maintenance of software related to a distributed and scalable OLAP engine ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Kylin was founded 2015-11-18 (10 years ago) There are currently 52 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - No new PMC members. Last addition was Xiaoxiang Yu on 2020-10-08. - No new committers. Last addition was Pengfei Zhan on 2024-11-12. ## Project Activity: - 3 incoming security issues under fix - exploring integration with OpenClaw - also considering to develop a new PMC in a few month ## Community Health: Nothing special. Seems there is increasing interest to Kylin in the sense of data semantics, translating the business language of data to the technical language, which enables non-technical users to talk to data. ----------------------------------------- Attachment AO: Report from the Apache Libcloud Project [Tomaž Muraus] ## Description Libcloud is a Python library that abstracts away differences among cloud provider APIs and provides a unified interface for interacting with compute, storage, load balancing, DNS, container, and backup services. ## Project Status Current project status: At risk The project continues to suffer from a lack of active committers and PMC members available to review contributions, process PRs, or shepherd releases. Since the last report although the current chair, Tomaz Muraus, is still a bit inactive, some PMC members are trying to reactivate the project. ## Project Activity During recent months, the project has received few contributions on GitHub (https://s.apache.org/h4y97). Activity has improved slightly in the past month as newly added PMC members have begun to re-engage. A notable contribution was a long-standing community PR that removed approximately 18 outdated drivers belonging to cloud providers that have closed or are no longer active. Two releases have been launched 3.9.0 and 3.9.1. ## Community Health As noted above, the project currently lacks sufficient active maintainers (committers and PMC members) to reliably review community contributions or handle the volume of incoming PRs. Download and usage statistics indicate that the library still has a significant user base: https://s.apache.org/k7tug Like Apache jclouds, Libcloud faces the challenge of being a "driver-oriented" project, where contributors often focus only on drivers they personally use, and fewer volunteers are willing to review or maintain drivers or core components unrelated to their own needs. This makes long-term maintenance more difficult. ## Membership Data * Apache Libcloud was founded on 2011-05-19 (almost 15 years ago). * There are currently 26 committers and 18 PMC members. * The Committer-to-PMC ratio is approximately 3:2. Community changes in the past quarter: * No new PMC members. Last PMC member addition were Zili Chen and Miguel Caballer (2026-01-24). * One new committer where added. Chojan Shang (2026-02-18). ----------------------------------------- Attachment AP: Report from the Apache Logging Services Project [Piotr Karwasz] ## Description: The mission of the Apache Logging Services project is to create and maintain of software for managing the logging of application behavior, and for related software components. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: No changes since the last report: - Founded: 2003-12-17 (22 years ago) - Committers: 49 (21 active) - PMC Members: 23 (15 active) - Committer-to-PMC ratio: 2:1 overall; 1:1 among active members Community changes, past quarter: - No new PMC members. Last addition was Jan Friedrich on 2024-08-07. - Grzegorz Dziadkiewicz was added as committer on 2026-04-13. - Ramanathan Muthu was added as committer on 2026-05-09. ## Project Activity: During the February–April 2026 quarter, the three active components (Log4j, Log4cxx, and Log4net) showed overall moderate activity, with a significant focus on coordinated security disclosures. Seven CVEs were published across the three components. The triage of the Log4j Bug Bounty Program backlog was completed during the quarter. The program was officially suspended on April 1st, with third-party triaging effectively ending in late January when the quota was exhausted. This allowed the team to refocus on feature work. The Trivy compromise caused additional churn: all third-party workflows now require pre-approval by INFRA, prompting a change in the architecture and update cadence of our reusable workflows. The project also discussed and tested branch and tag protection via the experimental GitHub Rulesets integration, as a preamble for future SLSA Source Provenance adoption. ### Log4cxx (activity: moderate) - Releases: - 1.7.0 on April 4th, 2026 ### Log4j (activity: moderate) - The project discussed the deprecation of the Kotlin and Scala bindings, since better alternatives in those languages exist and they can all reuse the Log4j Core engine. - Releases: - 2.25.4 on March 28th, 2026 - 2.26.0 on May 7th, 2026 ### Log4net (activity: moderate) - Releases: - 3.3.0 on February 20th, 2026 - 3.3.1 on April 19th, 2026 ## Community Health: The community remains active, with issues and pull requests opened daily. Three indicators worth flagging this quarter: 1. Cross-project coordination on security: Log4j, Log4cxx, and Log4net all shipped fixes for analogous XML 1.0 character-handling issues within a six-week window, evidence that the PMC's security workflow scales across the three runtimes. 2. New contributor engagement: notable first-time or returning contributors landed substantive PRs. Two new committers were added in the period. 3. Sustained drag from low-quality security reports: as detailed in the Project Activity section above, the volunteer cost of AI-generated reports is the dominant non-release pressure on the project, and the response is being shared openly with the wider ecosystem. ----------------------------------------- Attachment AQ: Report from the Apache Lucene.Net Project [Shad Storhaug] ## Description: Apache Lucene.NET is a port of the Lucene search engine library, written in C# and targeted at .NET runtime users. ## Project Status: Current project status: Ongoing with moderate activity Issues for the board: None ## Membership Data: Apache Lucene.Net was founded 2012-08-15 (14 years ago) There are currently 17 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 9:7. Community changes, past quarter: - No new PMC members. Last addition was Ron Clabo on 2022-03-03. - No new committers. Last addition was Nehan Pathan on 2025-09-23. ## Project Activity: Activity continues toward a final 4.8.0-beta00018 release, although much of the work is still being done in J2N and ICU4N. We have completed most of the work to upgrade J2N to System.Memory types to allow for more efficient memory management. There are only 3 remaining issues on the J2N 2.2 milestone. Lucene.Net is undergoing several breaking API changes to stabilize the API for the 4.8.0-beta00018 release. Some of the major tasks currently underway or have recently been completed are: - Adding code analyzers to automate code management tasks that are specialized for Lucene.NET. - Adding cancellation token support in SearcherManager and several of its dependencies. - Creating a new implementation of MMapDirectory to address several performance and durability concerns around index access when under heavy concurrent load. - Creating alternate lookup functionality in J2N collections that works not just on modern .NET, but also older target frameworks that we support. This allows us to avoid allocating temporary strings when looking up values in hash tables. - Creating an OpenStringBuilder implementation that manages a single contiguous block of memory, since the value in System.Text.StringBuilder cannot be converted to ReadOnlySpan due to multiple possible chunks of memory. - Creating a plan to compare API status between ICU4J and ICU4N so we can mark some APIs that are not ready unstable in order to push the release out before all of the APIs have been modernized. - Created low level hash table collections (OrderedHashSet and OrderedDictionary) to simulate the LinkedHashSet and LinkedHashMap Java collections. - Began adding support for using J2N and Lucene.NET with AOT trimming. - Creating an API comparison tool to help locate missing or mismatched APIs between Lucene and Luceene.NET. We are leaning heavily into AI to help automate most of the analysis and some of the code development tasks, and it is paying off in that we are moving at a much better pace. Most recent releases: Apache-Lucene.Net-4.8.0-beta00017 was released on 2024-10-29. Apache-Lucene.Net-4.8.0-beta00016 was released on 2022-02-17. Apache-Lucene.Net-4.8.0-beta00015 was released on 2021-10-29. ## Community Health: - builds@lucenenet.apache.org had a 94% decrease in traffic in the past quarter (3 emails compared to 46) - dev@lucenenet.apache.org had a 231% increase in traffic in the past quarter (318 emails compared to 96) - 40 commits in the past quarter - 6 code contributors in the past quarter - 38 PRs opened on GitHub, past quarter - 41 PRs closed on GitHub, past quarter - 21 issues opened on GitHub, past quarter - 17 issues closed on GitHub, past quarter We are starting to see some improvement in commit activity as we finish several of the remaining tasks for the Lucene.NET 4.8.0 port including directly addressing performance concerns, concurrency problems, and other issues that are important to end users. ----------------------------------------- Attachment AR: Report from the Apache ManifoldCF Project [Piergiorgio Lucidi] ## Description: The mission of ManifoldCF is the creation and maintenance of software related to Framework for connecting source content repositories to target repositories or indexes. ## Issues: Receiving any feedback from the community and the PMC is not easy. ## Membership Data: Apache ManifoldCF was founded 2012-05-15 There are currently 25 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, since last report in August: - No new PMC member. Last addition was made on 2023-08-03. - No new committers. Last addition was on 2019-08-17. ## Project Activity: Version 2.30 released in April including the upgrade to OpenJDK 21 and we removed some legacy connectors. We are currently working on the next release, replacing legacy thread pooling with Virtual Threads and implementing Structured Concurrency to improve the reliability of complex crawling jobs. A few users contacted me privately on LinkedIn, they are very interested to the new Roadmap. It seems that probably the new steering plan to make the project as an injection framework for vector databases is something that can attract new contributors and users. Recent releases: 2.30 was released on 2026-04-11 2.29 was released on 2025-09-12 SDK 1.02 released on 2025-02-10 2.28 was released on 2025-01-15 2.27 was released on 2024-09-26 2.26 was released on 2023-11-01 2.25 was released on 2023-06-01 ## Community Health: The project is still active, but the community is very small and not responsive. I would try to attract new contributors by implementing the new roadmap, but I don't have any expectation about the results. ----------------------------------------- Attachment AS: Report from the Apache Maven Project [Hervé Boutemy] ## Description: The mission of Maven is the creation and maintenance of software related to Java project management and comprehension tools ## Project Status: Current project status: ongoing with high activity. Issues for the board: none. ## Membership Data: Apache Maven was founded 2003-03-01 (23 years ago) There are currently 73 committers and 30 PMC members in this project. The Committer-to-PMC ratio is roughly 5:2. Community changes, past quarter: - No new PMC members. Last addition was Romain Manni-Bucau on 2023-10-16. - No new committers. Last addition was Christoph Läubrich on 2025-11-07. ## Project Activity: Releases since last report: - Apache Parent POM 38 was released on 2026-05-10 - Apache Maven Parent POMs 48 was released on 2026-05-10 - Apache Maven Invoker Plugin 3.10.1 was released on 2026-05-02 - Maven Resolver 2.0.17 was released on 2026-04-30 - Apache Maven Invoker Plugin 3.10.0 was released on 2026-04-22 - Apache Maven Script Interpreter 1.7 was released on 2026-04-14 - Apache Maven 3.9.15 was released on 2026-04-13 - Maven Doxia Sitetools 2.1.0 was released on 2026-04-08 - Maven Doxia 2.1.0 was released on 2026-03-21 - Apache Maven Daemon 1.0.5 was released on 2026-03-20 - Apache Maven Daemon 1.0.4 was released on 2026-03-16 - Apache Maven 3.9.14 was released on 2026-03-12 - Apache Maven JLink Plugin 3.3.0 was released on 2026-03-09 - Apache Maven 3.9.13 was released on 2026-03-06 - Maven Filtering 3.5.0 was released on 2026-03-05 - Maven Resources Plugin 3.5.0 was released on 2026-03-05 - Maven Shade Plugin 3.6.2 was released on 2026-03-05 - Apache Resource Bundles 1.8 was released on 2026-02-24 - Apache Maven Surefire 3.5.5 was released on 2026-02-23 - Maven Resolver 1.9.27 was released on 2026-02-23 - Maven Resolver 2.0.16 was released on 2026-02-23 - Maven Resolver 1.9.26 was released on 2026-02-16 - Maven Resolver 2.0.15 was released on 2026-02-16 - Apache Maven Dependency Plugin 3.10.0 was released on 2026-02-05 - Apache Maven Plugin Testing 3.5.1 was released on 2026-02-04 - Maven Compiler Plugin 3.0.15 was released on 2026-02-01 - Maven Compiler Plugin 4.0.0-beta-4 was released on 2026-02-01 - Apache Maven Dependency Analyzer 1.17.0 was released on 2026-01-29 - Apache Maven Build cache extension 1.2.2 was released on 2026-01-27 Since February, most release managers are using ATR to manage the 72h vote step of their releases: this remains an optional choice, both for release manager and voters, that does not change our overall release process, but permits some feedback to Tooling. An "ATR upload" Maven plugin is in preparation to ease release composition: it is owned by Tooling but maintained by Maven PMC https://github.com/apache/tooling-trusted-releases/issues/926 Maven 3.9.15 was released as last bugfix: we're working on Maven 3.10.x as the next/last stable Maven 3 branch, that prepares a smooth transition to future Maven 4.0 (by using the same Resolver 2 and getting a few structural changes). We updated our Maven logo to adapt to the new ASF brand. ## Community Health: Users mailing list activity remains quite low, even if a few key discussion happened there, like voting on the new logo. Development discussions happen both on mailing-list for taking decisions, and Slack for more diverse unstructured topics. ----------------------------------------- Attachment AT: Report from the Apache OpenOffice Project [Keith McKenna] ----------------------------------------- Attachment AU: Report from the Apache OpenWebBeans Project [Mark Struberg] ## Description: Apache OpenWebBeans is an ALv2-licensed implementations of the "Contexts and Dependency Injection for the Java EE platform" specifications which are defined as JSR-299 (CDI-1.0), JSR-346 (CDI-1.1 and CDI-1.2 MR), JSR-365 (CDI-2.0) and Jakarta CDI (CDI-4.0, CDI-4.1). The OWB community also maintains a small server as Apache Meecrowave subproject. Meecrowave bundles latest releases of the ASF projects Tomcat + OpenWebBeans + CXF + Johnzon + log4j2. ## Issues: There are no issues requiring board attention at this time. ## Activity: We did a new OWB-4.1.0 release targetting the new CDI-4.1 specification. Which also explains the uptick in activity. This will be followed up by a new Meecrowave release which we are currently preparing. ## PMC changes: - Currently 13 PMC members, 20 committers - No new PMC members. Last addition was Reinhard Sandtner on 2017-10-09. - Jonathan Gallimore was added as committer on 2025-12-04 ## Recent releases: - 4.1.o was released on 2026-05-03. - meecrowave-2.0.0 was released on 2025-10-21. - 2.0.28 was released on 2025-05-19. ----------------------------------------- Attachment AV: Report from the Apache OpenWhisk Project [Dave Grove] ## Description: The mission of Apache OpenWhisk is the creation and maintenance of software related to a platform for building serverless applications with functions ## Project Status: Current project status: Dormant Issues for the board: None ## Membership Data: Apache OpenWhisk was founded 2019-07-16 (7 years ago) There are currently 54 committers and 22 PMC members in this project. The Committer-to-PMC ratio is roughly 7:3. Community changes, past quarter: - No new PMC members. Last addition was Cosmin Stanciu on 2022-02-22. - No new committers. Last addition was Luke Roy on 2023-03-06. ## Project Activity: There was no development activity in the last quarter. The most recent releases were part of a wave of openwhisk-runtime releases made in August/September 2024: openwhisk-runtime-java-1.20.0 was released on 2024-09-23. openwhisk-runtime-php-1.21.0 was released on 2024-09-23. openwhisk-runtime-python-1.20.0 was released on 2024-09-23 openwhisk-runtime-swift-1.19.0: was released on 2024-09-23 openwhisk-runtime-dotnet-1.18.0: was released on 2024-09-13 openwhisk-runtime-docker-1.16.0: was released on 2024-09-07 openwhisk-runtime-nodejs-1.23.0: was released on 2024-09-07 openwhisk-runtime-go-1.25.0: was released on 2024-09-05 ## Community Health: There are sufficient PMC members paying attention to handle security issues, and answer the relatively low volume of user questions that we get (mainly via GitHub issues). With the exception of a small number of academic research projects, users of OpenWhisk have moved on to other serverless platforms. However, the Apache OpenServerless (incubating) project remains active and packages Apache OpenWhisk as one of its components. It is not clear to me whether there is sufficient interest in OpenServerless to revive activity in OpenWhisk or what would happen to OpenServerless if OpenWhisk were to retire to the Attic. ----------------------------------------- Attachment AW: Report from the Apache Ozone Project [Sammi Chen] ## Description Apache Ozone is a scalable, redundant, and distributed object and file store, designed to scale to billions of objects/files and run on clusters of thousands of nodes. Ozone supports S3 compatible object APIs as well as a Hadoop Compatible File System implementation. ## Issues None. ## Membership Data - Apache Ozone was founded 2020-10-21. - There are currently 89 committers and 43 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. - In the past quarter, Gargi Jaiswal was added as committer on 2026-04-28 Jheng-Sing Chen was added as committer on 2026-04-11 Saketa Chalamchala was added as committer on 2026-04-09 ## Project Activity - Snapshot phase 4 (HDDS-13747), further Scale up Snapshot Operations, is finished. Team is working on phase 5(HDDS-15130), Efficient Snapshot Diff. - Client side streaming read(HDDS-10338) development is close to finishing. - Security Token Service(HDDS-13323), builds a Amazon AWS Security Token Service (STS) API compatible service in Ozone, to support hybrid cloud usage for Ozone. Development is ongoing on the feature branch. - OM HA: Support Follower Read(HDDS-14424), an effort to allow clients to read from OM followers, development continues. - Zero Downtime Upgrade(HDDS-14496) design is finalized, and development is in progress. - Container and volume scanners enhancement phase 3(HDDS-14071), a few new issues found recently and addressed. - A comprehensive guide created for On Prem Apache Ozone Installation(HDDS-13869) is finished. It includes dependencies and prerequisites, where to download the released version, single node and HA mode deployment guide, OS and JDK recommendations. - Ozone documentation site(https://deepwiki.com/apache/ozone) powered by platform DeepWiki(HDDS-15157). - S3 Compatibility - Ozone S3 gateway Phase 4(HDDS-12716), including presigned URL support for all major S3 operations, etc. - S3 conditional requests support(HDDS-13117) is under development. Get, Head, Copy, Delete & Put Object will be supported. - Code cleanup and refactor, move server-only code out of common(HDDS-12352) is finished. - Fix intermittent failure unit and integration test is also ongoing(HDDS-9931). - Iceberg integration, Ozone's native implementation of Iceberg RewriteTablePath (HDDS-14937), which rewrite path starts with "ofs://" to "s3://" or "s3a://", has started the implementation. - Ozone Event Notification Support(HDDS-13513), provides an event notification mechanism for Ozone, to notify event receiver specific Ozone write type operations. Development continues on the feature branch. - Tracing is migrating from OpenTracing to OpenTelemetry as the OpenTracing project is deprecated(HDDS-13679). - Interactive Ozone shell is enhanced by including and allowing most of Ozone commands(HDDS-11825). - Ozone 2.2.0 release discussion is kicked off. - Following are the feature design documents shared in the community, which either are under review or require review. - OM multiraft feature(HDDS-15069) - EC container decommission speed up(HDDS-15014) - S3 signed multi chunks payload verification(HDDS-12542) - Ozone Storage Policy(HDDS-11233) ## Releases Data - 1.0.0 was released on 2020-09-02. - 1.1.0 was released on 2021-04-20. - 1.2.0 was released on 2021-11-17. - 1.2.1 was released on 2021-12-22. - 1.3.0 was released on 2022-12-18. - 1.4.0 was released on 2024-01-19. - 1.4.1 was released on 2024-11-24. - 2.0.0 was released on 2025-04-30. - 2.1.0 was released on 2025-12-31. ## Community Health Last board report was sent on 11th Feb 2026. Since last report, - 33 code contributors who have commits in the past quarter (-8%) - dev@ozone.apache.org had 60 emails in the past quarter (-47%) - 385 PRs opened on GitHub, past quarter(-8.8%) - 375 PRs closed on GitHub, past quarter(-22.2%) - 302 commits in the past quarter(-17.5%) Note: The commit & PR count excludes the ones from user "app/dependabot", who has many commits for dependency jar version upgrade. ----------------------------------------- Attachment AX: Report from the Apache Perl Project [Steve Hay] ## Description: The mission of Perl is the creation and maintenance of software related to Dynamic websites using Perl ## Project Status: Current project status: At risk Issues for the board: The project may not have sufficient oversight from the PMC ## Membership Data: Apache Perl was founded 2000-03-10 (26 years ago) There are currently 21 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Steve Hay on 2012-03-01. - No new committers were added. ## Project Activity: The last release was mod_perl-2.0.13 on 2023-10-21. The unfortunate demise of apreq was brought up on the mod_perl mailing lists lists, with two significant revelations: Firstly, my message to the PMC asking if we have enough skills to take on apreq rather than see it moved to the Attic only got one reply, which must call into question whether we even have enough people around to continue maintaining mod_perl itself. Secondly, it came to light that whilst the official mod_perl project's development has long been in a very quiet maintenance mode, some development has taken place elsewhere in a fork on GitHub A PR has been sent to the Apache mirror of mod_perl on GitHub, which I wasn't aware of until recently since development is normally only via SVN. ## Community Health: Mailing list traffic was slightly up due to the apreq announcement. There are clearly users of mod_perl (and apreq) still out there, but they might be better served by the new GitHub fork if we can't even muster replies from 3 PMC members here. apreq has also been forked by the same GitHub author, and also has some development activity which clearly now won't be merged back to the official ASF version, so even if mod_perl is kept alive here users wanting apreq as well will still have to go to GitHub to get the latest version of that. ----------------------------------------- Attachment AY: Report from the Apache Phoenix Project [Istvan Toth] ## Description: The mission of Phoenix is the creation and maintenance of software related to High performance relational database layer over Apache HBase for low latency applications ## Project Status: Current project status: Ongoing Issues for the board: Our former Chair, Istvan Toth, stepped down for health reasons. We are saddened to report his recent passing, after a brief illness. A VOTE for new PMC chair was completed, proposing Viraj Jasani (vjasani) be appointed to the position of VP, Apache Phoenix. The vote passed with 11 +1 binding votes and no vetos: https://lists.apache.org/thread/dn9gd8ncpxkj5t457gbct7655xnp78sk Phoenix 5.3.1 release is in progress. We expect to complete the release before the end of the month. ## Membership Data: Apache Phoenix was founded 2014-05-20 (12 years ago) There are currently 60 committers and 38 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members. Last addition was Jacob Isaac on 2023-11-06. - No new committers. Last addition was Nihal Jain on 2025-08-05. ## Project Activity: Development activity remains average. Feature development is concentrated on the consistent failover feature, improving CDC (Change Data Capture), and support for the DynamoDB connector/adapter. Recent major features also include the eventually consistent global secondary indexes. Some recent enhancements include new metrics at client and server side. Recent releases: thirdparty-2.2.0 was released on 2025-12-10. 5.3.0 was released on 2025-10-03. phoenix-omid-1.1.3 was released on 2025-04-04. 87 JIRA tickets were opened and 56 were closed in the past quarter. dev@phoenix.apache.org had a 100% increase in traffic in the past quarter (338 emails compared to 169) issues@phoenix.apache.org had a 79% increase in traffic in the past quarter (542 emails compared to 302) ## Community Health: Overall community health is acceptable. Most of the development is done by our core team of about a dozen active developers. ----------------------------------------- Attachment AZ: Report from the Apache Pinot Project [Kishore G] ## Description: The mission of Apache Pinot is the creation and maintenance of software related to a distributed OLAP datastore that provides real-time analytics for a wide variety of use cases. ## Project Status: Current project status: Ongoing (high activity) Issues for the board: None ## Membership Data: Apache Pinot was founded 2021-07-20 (5 years ago) There are currently 48 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - Yash Mayya was added to the PMC on 2026-05-04 - Aman Khanchandani was added as committer on 2026-04-13 - Raghav Yadav was added as committer on 2026-04-13 - Harnoor Singh was added as committer on 2026-04-08 - Shaurya Chaturvedi was added as committer on 2026-02-23 ## Project Activity: Recent releases: 1.5.0 (2026-04-15): 1,100+ commits. Highlights include Multi-Stage Query Engine improvements (UNNEST, enriched joins, aggregation rewrites), Upsert enhancements (offline table support, commit-time compaction, xxhash compression), a new Federation / Multi-Cluster Routing framework, Kafka 4.x support, real-time auto-reset, Time Series Engine enhancements, new indexing capabilities (N-gram, IFST, combined Lucene), Query Resource Isolation, plus performance, security, and bug fixes. 1.4.0 was released on 2025-09-16. The gap to 1.5.0 was longer than ideal; we've since automated several previously manual, error-prone release tasks to support a more regular cadence. ## Community Health: Day-to-day project discussion happens primarily on Slack and GitHub, with the dev@ and user@ lists used for releases, votes, and announcements as expected. Over the past three months: Slack: 2700 messages, 170 monthly active users GitHub: 700+ PRs opened, 500+ merged The Apache Pinot "Year in Review" webinar in February 2026 drew 55 live attendees, featuring community use cases and committer talks on the past year's features. The virtual Apache Pinot Meetup group has held 5 events since November 2025. ----------------------------------------- Attachment BA: Report from the Apache POI Project [Dominik Stadler] Report from the Apache POI committee [Dominik Stadler] ## Description: - Apache POI is a Java library for reading and writing Microsoft Office file formats. The Apache POI PMC also handles bugfixes for the XMLBeans project: XMLBeans is a tool that allows you to map XML files to generated Java classes via XML Schema definitions. ## Project Status: - Overall: Low activity/Mostly maintenance only - Activity on the project is low with no-one willing/able to invest time to look for new committers. This project is in a mostly-maintenance mode unless someone new starts to invest time. - Note: None of the active committers wants to spend time looking for new people, so suggesting to reach out to others or invest in "marketing" will likely not lead to much improvement. - The project still has enough active PMC members to vote on issues and perform releases ## Membership Data: Apache POI was founded 2007-05-16 (19 years ago) There are currently 41 committers and 34 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 Marius Volkhart on 2020-12-27. - No new committers. Last addition was Marius Volkhart on 2020-12-19. ## Project Activity: - Upgraded to minimum Java 11, we likely will go to Java 17 for the next major release 6.x - Various bug-fixes, some from external contributes via GitHub PRs ## Project Release Activity: - 5.5.1 was released on 2025-11-30. - 5.5.0 was released on 2025-11-15. - 5.4.1 was released on 2025-04-06. - XMLBeans-5.3.0 was released on 2024-12-13. ## Community Health: - There are a few bug-reports and pull-requests which indicates that Apache POI is still in use. Questions via email or on Stackoverflow usually get answers. - Bug-numbers slowly increase over time. Some newly reported issues are fixed, but we usually get more bugs/questions reported than are addressed by the small number of active committers, so some bugs do not get attention any more. - We have a very small number of active committers. There are very few potential candidates and no-one plans to spend effort to go looking for new ones. ### XMLBeans - It seems there are is a small but active set of users of XMLBeans besides Apache POI itself. - Bug influx for XMLBeans is very low in general because it is a stable project in maintenance-only mode. ## Bug Statistics: ### Apache POI - 637 bugs are open overall (+3) - Having 146 enhancements (+-0) - Thus having 491 actual bugs (+3) - 120 of these are waiting for feedback (-1) - Thus having 371 actual workable bugs (+4) - 4 of the workable bugs have patches available (+4) - Distribution of workable bugs across components: {XSSF=105, HSSF=80, SS Common=47, HWPF=36, XSLF=32, XWPF=18, POI Overall=15, SXSSF=8, POIFS=7, HSMF=6, OPC=6, HPSF=4, HSLF=3, XDDF=2, HPBF=1, SL Common=1} - GitHub: Open Issues: 16 Open Pull-Requests: 30 ### Apache XMLBeans - 168 open issues (+1) - 120 Bug (+-0) - 28 Improvement (+-0) - 15 New Feature (+-0) - 3 Task (+1) - 2 Wish (+-0) ----------------------------------------- Attachment BB: Report from the Apache Polaris Project [Jean-Baptiste Onofré] ## Description: The mission of Apache Polaris is the creation and maintenance of software related to a catalog for data lakes. It provides new levels of choice, flexibility and control over data, with full enterprise security and Apache Iceberg interoperability across a multitude of engines and infrastructure ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Polaris was founded 2026-02-18 (3 months ago) There are currently 31 committers and 19 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - Sung Yun was added to the PMC on 2026-04-27 - Adam Christian was added as committer on 2026-03-07 - Adnan Hemani was added as committer on 2026-03-07 - Christopher Lambert was added as committer on 2026-03-11 - Danica Fine was added as committer on 2026-02-27 ## Project Activity: Apache Polaris 1.4.0 was released on April 23, 2026, making the project's first major release as fully graduated TLP. This release represents a significant milestone, with the project returning to a regalar monthly cadence following graduation. The 1.4.0 release highlights are: - Credential vending support for Azure and Google Cloud Storage backends - Catalog federation design advances, allowing Polaris to serve as a front for multiple catalog backends in multi-cloud environments (AWS, Azure, GCS) - S3 KMS encryption support for AWS-backed catalogs - Polaris Python CLI 1.4.0 released alongside the server distribution Quickly after, Apache Polaris 1.4.1 was released on May 1, 2026, as a security release, fixing 4 CVEs: - CVE-2026-42809 - CVE-2026-42810 - CVE-2026-42811 - CVE-2026-42812 The PMC worked efficiently on identifying, reporting, and fixing these security issues with the ASF security team and releasing a patch-version with the fixes. ## Community Health: Sung Yun has been elected as new PMC member on 2026_04-27. Post-graduation development has been highly active, with multiple design proposals advancing simultaneously on the dev mailing list (69% increase in traffic in the past quarter). We can note the following active design proposals in the community: - Apache Ranger Authorization RFC: the community proposes opt-in Ranger integration for organizations running Ranger alongside Hive, Spark, and Trino. It provides unified governance framework eliminating policy duplication. - OpenLineage integration: the community is discussing OpenLineage integration, around events, and proxy approaches. - AGENTS.md: the community discussed about adding AGENDS.md to the repository to provide agent-readable metadata. It improves the compatibility with AI coding tools and automated contribution workflows. This reflects a broader trend across the ASF projects to address AI tooling in the development workflow. In terms of event outreach, Iceberg Summit 2026 showed Apache Polaris features prominently as part of the open lakehouse ecosystem. Polaris Community Sprint gathered Polaris community members to discuss proposals. Also Iceberg Pre-Summit Meetup hosted by Bloomberg Engineering included Polaris representation. On the trademark part, the PMC is actively managing third-party use of the Polaris brand in compliance with The ASF branding guidelines. ----------------------------------------- Attachment BC: Report from the Apache Qpid Project [Robbie Gemmell] Apache Qpid is a project focused on creating software based on the Advanced Message Queuing Protocol (AMQP), currently providing a protocol engine library, message broker, and client libraries for C, C++, .Net, Go, Java/JMS, Python, and Ruby. # Releases: There were no new releases this quarter. # Community: - The main user and developer mailing lists continue to be active and JIRAs are being raised and addressed in line with prior activity levels. - There were no new PMC member additions in this quarter. The most recent new PMC member is Daniil Kirilyuk, added 22nd January 2024 - There were no new committer additions in this quarter. The most recent new committer is Daniil Kirilyuk, added 17th February 2023 # Development: - Broker-J continues to see more improvements, bug fixes, and dependency updates towards its next release, including updates to enable support for running on Java 25+. Work progresses on more improvements and bug fixes. - Updates continue towards a Proton 0.41.0 release in the coming weeks. An initial version of transaction support for the Proton C++ binding has been landed and some improvements to this are being worked on, along with various earlier improvements and bug fixes. - ProtonJ2 is working towards its 1.2.0 release with various improvements and bug fixes. Work also begun towards a 2.0.0 with a raised Java 17 minimum requirement and various code cleanup / improvements made. - Some bug fixes and dependency updates for Qpid JMS are being worked on towards its next releases. - Some improvements and bug fixes for proton-j are being worked on towards its next release for use in Qpid JMS and other components. # Issues: There are no Board-level issues at this time. ----------------------------------------- Attachment BD: Report from the Apache Ranger Project [Selvamohan Neethiraj] ----------------------------------------- Attachment BE: Report from the Apache RocketMQ Project [Xiaorui Wang] ## Description: The mission of Apache RocketMQ is the creation and maintenance of software related to a fast, low latency, reliable, scalable, distributed, easy to use message-oriented middleware, especially for processing large amounts of streaming data. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache RocketMQ was founded 2017-09-20 (8.5 years ago) There are currently 76 committers and 21 PMC members in this project. The Committer-to-PMC ratio is roughly 7:2. Community changes, past quarter: - No new PMC members. Last addition was Zhouxiang Zhan on 2023-09-21. - Xiao Yang was added as a new committer during this reporting period. ## Project Activity: Recent releases: - ROCKETMQ-5.5.0 was released on 2026-04-10. ## Community Health: Over the past quarter, the Apache RocketMQ community has continued to show a stable and healthy development trend. Activity on GitHub has stayed steady, with ongoing work across feature development and issue management. Contributions and issue resolutions remain well balanced, and pull requests are being reviewed and merged in a consistent and timely manner, reflecting smooth collaboration between contributors and maintainers. Contributor participation is still fairly distributed, with no clear dependence on a small group of individuals, which is a good sign of a decentralized and sustainable development model. Most of the changes are incremental, focusing on continuous improvements, bug fixes, and refinements to existing functionality rather than major architectural changes. Overall, no unusual patterns were observed during this period. The project continues to run with stable maintenance momentum and a predictable review and release rhythm, with a continued focus on reliability, operational stability, and steady ecosystem improvements. ----------------------------------------- Attachment BF: Report from the Apache Roller Project [Dave Johnson] ## Description: Apache Roller is a full-featured, Java-based blog server that works well on Tomcat, Postgres and MySQL, and is known to run on other Java servers and relational databases. Latest release is 6.1.5 on 2025-04-19. ## Project Status: The project is mostly dormant with most activity around updating dependencies, making sure the code runs on the latest Java releases and security fixes. No issues require board attention at this time. ## Membership Data: Apache Roller was founded 2007-02-20 (19 years ago) There are currently 12 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Michael Bien on 2021-05-24. - No new committers. Last addition was Yash Maheshwari on 2021-09-01. ## Project Activity: This was a quiet quarter. There has been some recent activity around dependency updates and security triage, but no new release since Roller 6.1.5. ## Community Health: The Roller community is small and quiet, but healthy enough to maintain Roller and make bug fix and security releases when necessary. We're always on the lookout for new contributors. ----------------------------------------- Attachment BG: Report from the Apache Santuario Project [Colm O hEigeartaigh] ## Description: The mission of Santuario is the creation and maintenance of software related to XML Security in Java and C++ ## Project Status: Current project status: The Java project is actively maintained and PRs are getting merged and releases made. Issues for the board: Nothing to report ## Membership Data: Apache Santuario was founded 2006-06-27 (20 years ago) There are currently 18 committers and 7 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. Community changes, past quarter: - No new PMC members. Last addition was Daniel Kulp on 2018-10-01. - No new committers. Last addition was Joze Rihtarsic on 2024-05-14. ## Project Activity: It was a quiet quarter for the project. We have a number of open pull requests to review and then we will get new releases done this quarter. Last releases: - Apache Santuario - XML Security for Java 3.0.6 was released on 2025-04-11. - Apache Santuario - XML Security for Java 4.0.4 was released on 2025-04-11. ## Community Health: Apache Santuario is a mature and stable project that has reached a point where not too many fixes are required, as it is a set of implementations of some specifications that are quite old now. It is actively managed by the PMC ----------------------------------------- Attachment BH: Report from the Apache SDAP Project [Nga Thien Chung] ## Description: The mission of Apache SDAP is the creation and maintenance of software related to an integrated data analytic center for Big Science problems ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache SDAP was founded 2024-04-16 (2 years ago) There are currently 23 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - No new PMC members. Last addition was Joshua Garde on 2026-01-12. - No new committers. Last addition was Joshua Garde on 2026-01-08. ## Project Activity: Last SDAP release was 1.4.0 on 2024-11-04. Progress in getting an SDAP release out the door is slow going. SDAP is still dependent on python3.9 which has already reached EOL. SDAP’s deployment also depends on bitnami charts that are no longer supported. The community will prioritize pushing for these necessary updates. There is a work in progress py311 branch of sdap-nexus. ## Community Health: Since last quarter, dev@sdap.apache.org had 2 new threads. ### Contributors Since last quarter, the SDAP community has merged 2 PR and created/updated 2 Jira issues. The SDAP community has kept up with its monthly community meetings with decent turnout. Work on integrating SDAP with the new in situ data services components that leverage Sedona has restarted. ----------------------------------------- Attachment BI: Report from the Apache Sedona Project [Jia Yu] ## Description: The mission of Apache Sedona is the creation and maintenance of software related to a big geospatial data processing engine. It provides an easy to use APIs for spatial data scientists to manage, wrangle, and process geospatial data ## Project Status: Current project status: Ongoing Issues for the board: No issues ## Membership Data: Apache Sedona was founded 2022-12-20 (3 years ago) There are currently 25 committers and 20 PMC members in this project. The Committer-to-PMC ratio is 5:4. Community changes, past quarter: - Dewey Dunnington was added to the PMC on 2026-04-28 - Liang Geng was added as committer on 2026-04-28 ## Project Activity: Sedona 1.9.0 was released on April 22, 2026. This is a major release with new features, improvements, and bug fixes. Key highlights include Spark 4.1 support, a new proj4sedona library for CRS transformation that replaces the previous PROJ dependency for many transformations, and a new family of Bing Tile spatial functions for tile-based analytics. The release also extends the OSM PBF reader with additional metadata fields, adds _metadata hidden column support for the Shapefile and GeoPackage DataSource V2 readers, expands the GeoPandas-style API on Spark with additional geometry operations, and includes numerous bug fixes and documentation improvements. SedonaDB 0.3.0 was released on March 10, 2026. This release of Apache Sedona's single-node spatial analytics engine introduces larger-than-memory spatial joins, allowing SedonaDB to operate on datasets that exceed available memory, and adds row-level CRS support so that geometries within a single column can carry independent coordinate reference systems. The release also includes broader spatial SQL coverage and performance improvements. SpatialBench 0.2.0 was released on February 23, 2026. This release of Apache Sedona's geospatial SQL benchmark suite adds S3 write support for data generation, nightly benchmark support for DuckDB and SedonaDB, Spatial Polars integration, and an automated benchmark GitHub Action for comparing spatial libraries across runs. ## Community Health: The community remains healthy with active engagement across GitHub, the dev mailing list, and Discord. The Apache Reporter Community Health Score (Chi) is 10.00 (Super Healthy). In recognition of sustained contributions, we promoted Dewey Dunnington to the PMC and added Liang Geng as a new committer this quarter. JIRA activity remains low by design — the project transitioned from JIRA to GitHub Issues in 2025, so most issue traffic now flows through GitHub. Traffic on the issues@ mailing list grew 13% quarter-over-quarter (2431 vs 2142 emails), reflecting continued contributor activity on PRs and issues. ----------------------------------------- Attachment BJ: Report from the Apache Serf Project [Daniel Sahlberg] ## Description: The mission of the Apache Serf project is creating and maintaining of software related to HTTP and associated protocols. ## Project Status: The project has sufficient PMC oversight. There are no threats to the sustainability or resilience of the project, although the project is in general very much dormant due to lack of need/requirements from our users. The project has no requests for the Foundation. ## Membership Data: Apache Serf was founded 2015-08-18 (11 years ago) There are currently 17 committers and 15 PMC members in this project. The Committer-to-PMC ratio is roughly 9:8. Community changes, past quarter: - No new PMC members. Last addition was Graham Leggett on 2025-06-27. - No new committers. Last addition was Graham Leggett on 2025-06-28. ## Project Activity: Ongoing discussion about releasing the next minor release, Serf 1.5.0. Recent releases: * 1.3.10 was released on 2023-05-31. * 1.3.9 was released on 2016-08-31. ## Community Health: Serf and Subversion have a significant overlap of committers and PMC members and Subversion is the only (known) open source project using Serf. New features in Subversion are therefore the primary driver for development in Serf. After significant activity last quarter, activity died down due to lack of time. There are still plans for making a new minor release in the near future. One security issue was reported via security@a.o, however after review it only exist in non-released code and will be handled before the next release. Our community is fully volunteer-driven and we would like to thank everyone for their support. ----------------------------------------- Attachment BK: Report from the Apache ServiceComb Project [Zhangjian He] ## Description: The mission of Apache ServiceComb Java-Chassis is the creation and maintenance of software related to a Java microservice framework and SDK. It implements OpenAPI-based service contracts and provides service registration, service discovery, dynamic routing, observability, and service governance features for Java microservices. ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache ServiceComb was founded 2018-10-17 (7+ years ago). There are currently 38 committers and 22 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. The apache/servicecomb-java-chassis repository was created on 2017-05-18 (9 years ago). The repository currently has 1.9k+ stars, 821 forks, 129 watchers, 200 open issues, and 24 open pull requests on GitHub. Community changes, past quarter: - No new PMC members. Last addition was Cheng Youling on 2024-10-12. - No new committers. Last addition was Zhangjian He on 2025-01-28. ## Project Activity: ServiceComb Java-Chassis 2.9.4 was released on 2026-04-25. ServiceComb Java-Chassis 2.8.31 was released on 2026-03-16. Since 2026-02-18, 21 pull requests have been merged across the master and maintenance branches. The main changes are summarized below: ## Maintenance / Dependency Updates - [#5126] - Update JDK version - [#5121] - Bump micrometer-bom from 1.16.3 to 1.16.4 - [#5108] - Bump Spring Boot dependencies from 3.4.5 to 3.4.13 and Vert.x dependencies from 4.5.15 to 4.5.24 - [#5105] - Bump jetcd-core from 0.8.5 to 0.8.6 - [#5104] - Bump jersey.version from 4.0.0 to 4.0.2 - [#5102] - Bump nacos-client from 3.1.0 to 3.1.1 - [#5095] - Bump vertx-dependencies from 5.0.1 to 5.0.8 - [#5088] - Upgrade Netty/Vert.x version ## Bug / Behavior Fixes - [#5131] - Fixed incorrect ProduceProcessor selection when produces is null - [#5109] - Fix unit tests with Vert.x update - [#5093] - Fix servicecomb.credentials.akskEnabled=false cannot close log issue - [#5092] - Keep registry cache so instances remain available after microservice and engine recovery - [#5091] - SSLOption/KeyPairUtils uses Environment to get configs ## Project Management / Cleanup - [#5129] - Project management of the Archaius component - [#5103] - Bump exec-maven-plugin from 3.6.2 to 3.6.3 - [#5101] - Bump mockito-bom from 5.20.0 to 5.21.0 - [#5099] - Bump license-maven-plugin from 2.7.0 to 2.7.1 - [#5098] - Bump assertj-core from 3.27.6 to 3.27.7 - [#5097] - Bump dependency-check-maven from 12.1.9 to 12.2.0 - [#5096] - Bump micrometer-bom from 1.16.0 to 1.16.3 - [#5094] - Bump maven-compiler-plugin from 3.14.0 to 3.15.0 ## Community Health: Overall, community health is good. ServiceComb Java-Chassis made 2 releases in the past quarter, and the work focused on maintaining the 2.8.x/2.9.x release lines, upgrading dependencies, and fixing behavior around registry cache availability, SSL configuration handling, credentials logging, and request processor selection. Development is steady, although activity is still driven by a small number of maintainers. Continuing to attract new contributors would help broaden long-term maintenance capacity. ----------------------------------------- Attachment BL: Report from the Apache ShardingSphere Project [Liang Zhang] ## Description: The mission of Apache ShardingSphere is the creation and maintenance of software related to a database clustering system providing data sharding, distributed transactions, and distributed database management ## Project Status: Current project status: OK Issues for the board: None ## Membership Data: Apache ShardingSphere was founded 2020-04-15 (6 years ago) There are currently 62 committers and 22 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Longtao Jiang on 2024-03-28. - No new committers. Last addition was Chenyang Ma on 2024-05-27. ## Project Activity: Apache ShardingSphere maintained a steady development and release cadence during this quarter and published version 5.5.3. The work in this release can be summarized in several areas: continued security fixes and stability hardening to ensure the reliability of core execution paths in production scenarios; ongoing improvement of the overall pluggable architecture and module decoupling to further enhance the extensibility of database types, feature components, and governance capabilities; enhanced JDBC and Proxy integration and compatibility to support a broader database ecosystem and more deployment scenarios; and continued expansion of SQL parsing, routing, rule management, and end-to-end verification capabilities to improve multi-dialect support, operational experience, and overall quality assurance. Overall, the project continued to advance with a balanced focus on core capability evolution, compatibility improvement, and engineering quality. ## Community Health: Community health remains stable overall. Although there were no new PMC members or committers during the reporting period, existing maintainers and contributors continued to collaborate steadily, and development, review, and release activities all progressed normally. In addition to the core contributors continuing to take on the main maintenance responsibilities, external contributors also remained involved in areas such as dialect compatibility, test improvements, and bug fixes, indicating that the project still has a healthy level of contribution activity. At the same time, the project has entered a more mature and stable stage, so its activity level is naturally lower than during its earlier growth phase. ----------------------------------------- Attachment BM: Report from the Apache ShenYu Project [Yu Xiao] ## Description: The mission of Apache ShenYu is the creation and maintenance of software related to a Java native API Gateway for service proxy, protocol conversion and API governance ## Project Status: Current project status: Good Healthy. Issues for the board: There are no issues requiring board attention. ## Membership Data: Apache ShenYu was founded 2022-07-20 (4 years ago) There are currently 60 committers and 26 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - No new PMC members. Last addition was Hongyu Liu on 2025-05-15. - Siheng Yu was added as committer on 2026-02-24 ## Project Activity: Software development activity: - We added CORS support with configurable allowed headers. - We fixed websocket client spec builder reuse in plugin config. - We fixed selector population logic in RuleServiceImpl. - We fixed console rule-creation bug. - We fixed MCP streamable behavior . - We fixed PluginEnum sort values with schema.sql. - We refactored aiRequest / aiResponse models to support async use cases. - We refactored remove Shenyu trie cache. - We refactored remove Java 18 CI  Meetups and Conferences: - Community meetings(2) to discuss development tasks and how to build an open governance community. ## Community Health: Overall community health is good. Since the last report, add +2 contributors added (currently:427). add +2 subscribers to dev@shenyu.apache.org mailing (currently:512) ----------------------------------------- Attachment BN: Report from the Apache SIS Project [Martin Desruisseaux] ## Description: The mission of Apache SIS is the creation and maintenance of software providing data structures for developing geospatial applications compliant with the model of OGC/ISO international standards. ## Project Status: Current project status: ongoing with high activity. Issues for the board: no new issue (no development on the subject raised in last report). ## Membership Data: Apache SIS was founded 2012-09-19 (14 years ago) There are currently 22 committers and 17 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 Alexís Manin on 2021-05-27. - No new committers. Last addition was Bruno P. Kinoshita on 2021-06-23. ## Project Activity: Talks about Apache SIS have been accepted in two conferences: FOSS4G in Hiroshima in September [1], and Community Over Code in October. Some works and talks about SIS are also done in an OGC code sprint this week [2] (this one is not a joint ASF/FOSS4G/OGC code sprint). Contributions to Apache Maven (necessary for making SIS easier to build) are on pause for now. We need a release of Maven 4 before to continue the work on Java modules support. [1] https://2026.foss4g.org/ [2] https://s.apache.org/jifb9 ## Community Health: Contributions from different authors are increasing in the incubator part of Apache SIS, but are slow to be reviewed before merge in the endorsed part of SIS. This is a problem difficult to resolve, as the reviews always raise important issues that need to be fixed before merging. ----------------------------------------- Attachment BO: Report from the Apache Solr Project [Alessandro Benedetti] ## Description: The mission of Apache Solr is the creation and maintenance of software related to highly scalable distributed document search and analytics ## Project Status: Current project status: Ongoing with moderate activity. Issues for the board: none. ## Membership Data: Apache Solr was founded 2021-02-17 (5 years ago) There are currently 102 committers and 62 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Christos Malliaridis on 2025-11-23. - Ilaria Petreti was added as committer on 2026-03-16 - Lucas Kot-Zaniewski was added as committer on 2026-03-21 - Rahul Goswami was added as committer on 2026-02-09 ## Project Activity: Recent releases: 10.0.0 was released on 2026-03-03. Areas of development & interest: * API renovation and migration continue * Dense vector search improvements and new features are catching up with Apache Lucene (thanks to various sponsors) * Add Case Studies section to the Solr website * Apache Solr MCP server * Solr orbit - Performance benchmarking * Working to address many security vulnerabilities that were reported recently ## Community Health: (as at 2026-05-05) builds@solr.apache.org had a 20% increase in traffic in the past quarter (3945 emails compared to 3285): dev@solr.apache.org had a 2% increase in traffic in the past quarter (303 emails compared to 295): users@solr.apache.org had a 22% increase in traffic in the past quarter (152 emails compared to 124): - Conferences and events: - European Conference on Information Retrieval (ECIR '26) features a talk on Apache Solr (Exploring Neural IR in Europeana) - https://ecir2026.eu/programme/accepted-papers - Community Over Code talks have been scheduled and presents a great search track featuring Solr The community feels healthy, active, and with new contributors (that hopefully will become committers and PMC members). ----------------------------------------- Attachment BP: Report from the Apache Spark Project [Matei Zaharia] ## Description: Apache Spark is a fast and general purpose engine for large-scale data processing. It offers high-level APIs in Java, Scala, Python, R and SQL as well as a rich set of libraries including stream processing, machine learning, and graph analytics. ## Project Status: - Apache Spark 4.2.0 is currently in the QA phase - Released Apache Spark 4.2.0-preview5 on May 2, 2026. - Released Apache Spark Connect Swift Client 0.6.0 on Apr 10, 2026. - Released Apache Spark 4.2.0-preview4 on Apr 8, 2026. - Released Apache Spark Kubernetes Operator 0.8.0 on Mar 15, 2026. - Released Apache Spark 4.2.0-preview3 on Mar 13, 2026. - Several SPIPs were accepted since the previous report: 1. Extending the Spark 3.5 LTS Period With Security Fixes 2. DSV2 Enhanced Partition Stats Filtering 3. Change Data Capture (CDC) Support 4. Auto CDC Support for Apache Spark 5. Unified UDF Execution Protocol and Worker Specification for Multi-Language UDFs - Notable changes adopted by community: 1. GitHub Issues opened as an experimental issue-tracking option alongside JIRA 2. A buffer / grace period before adopting upstream dependency upgrades 3. Drop support for PyPy in PySpark 4. Replacing black with ruff as the Python formatter ## Trademarks: - No changes since last report. ## Latest Releases: - Spark 4.0.2 was released on Feb 5, 2026 - Spark 3.5.8 was released on Jan 23, 2026 - Spark 4.1.1 was released on Jan 9, 2026 ## Committers and PMC: - The latest committer was added on Feb 9, 2026 (Cheng Pan). - The latest PMC member was added on Jan 21, 2025 (Jie Yang). ----------------------------------------- Attachment BQ: Report from the Apache StormCrawler Project [Richard Zowalla] ## Description: The mission of Apache StormCrawler is the creation and maintenance of software related to an open source collection of resources for building low-latency, scalable web crawlers on Apache Storm ## Project Status: Current project status: Active Issues for the board: None ## Membership Data: Apache StormCrawler was founded 2025-05-21 (a year ago) There are currently 11 committers and 6 PMC members in this project. The Committer-to-PMC ratio is roughly 2:1. Community changes, past quarter: - Dávid Szigecsán was added to the PMC on 2026-03-03 - No new committers. Last addition was Dávid Szigecsán on 2025-09-23. A new committer candidate is currently under vote. ## Project Activity: Contributions from external participants continue to arrive, including from first-time contributors. We are also seeing encouraging traffic on the revamped documentation site introduced with the most recent release, which suggests the improved structure and accessibility are helping users find what they need. We hope this will continue to lower the barrier to entry and bring more contributors into the project over time. On the trademark front, we have finalized a logo for the project following feedback from M&P. With the logo now in place, we plan to move forward with the remaining steps of the trademark process. Recent releases: stormcrawler-3.5.1 was released on 2026-01-25. stormcrawler-3.5.0 was released on 2025-09-16. stormcrawler-3.4.0 was released on 2025-06-27. ## Community Health: The StormCrawler community remains active and stable. Pull requests from external contributors continue to arrive, and engagement with the new documentation is a positive signal for community growth. Since the last report, we have added a new PMC member, bringing the PMC to six, which partially addresses the concern raised previously about the small size of the PMC and the difficulty of gathering votes within short timeframes. Discussion of an additional committer is underway on the private list, which would further strengthen the contributor base. Ongoing documentation improvements remain a focus to ensure newcomers can participate easily and existing contributors stay engaged. ----------------------------------------- Attachment BR: Report from the Apache StreamPipes Project [Philipp Zehnder] ## Description: The mission of Apache StreamPipes is the creation and maintenance of software related to a self-service Industrial IoT toolbox which enables non-technical users to connect, analyze and explore IoT data streams ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache StreamPipes was founded 2022-11-16 (3 years ago) There are currently 34 committers and 16 PMC members in this project. The Committer-to-PMC ratio is roughly 9:4. Community changes, past quarter: - No new PMC members. Last addition was Sven Oehler on 2025-10-30. - Xinhao Liu was added as committer on 2026-04-10 ## Project Activity: * Improved OPC UA support, including support for events and complex data types * Implemented an initial NATS-based broker communication mode for core-to-extension requests, enabling HTTP-free extension connectivity while preserving backward compatibility through configurable dual transport support. * Added functionality to directly import CSV data into data sets. ## Community Health: * Presentationat Community Over Code in Glasgow. * Community members plan to participate in the hackathon at Community Over Code ----------------------------------------- Attachment BS: Report from the Apache Struts Project [René Gielen] ## Description: The Apache Struts MVC framework is a solution stack for creating modern and elegant action-based Java web applications. It favours convention over configuration, is extensible using a plugin architecture, and ships with plugins to support patterns and technologies such as REST, AJAX and JSON. ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Struts was founded 2004-03-17 (22 years ago) There are currently 60 committers and 23 PMC members in this project. The Committer-to-PMC ratio is roughly 8:3. Community changes, past quarter: - No new PMC members. Last addition was Kusal Kithul-Godage on 2024-02-24. - No new committers. Last addition was Kusal Kithul-Godage on 2023-08-03. ## Project Activity: The Struts team made two releases in the reporting period: - Apache Struts IntelliJ IDEA plugin ver. 253.18970.1 (2026-02-11) [1] - Struts 6.9.0 - Bug Fix and Improvements Release (2026-04-17) [2] The last Struts framework releases of maintained branches were - Struts 7.1.1 - Bug Fix, Improvements and Feature Release (2025-10-18) The last Struts releases besides the core framework were - Struts Annotations 2.0.0 - Enhancements and JDK 17 support (2025-07-03) - Struts Master 15 - Apply Apache Parent POM and plugin upgrades (2024-04-06) Within the last quarter, we saw activity levels similar to the preceding period. Most notably, we saw the first release of the IntelliJ Struts Plugin after its adoption from Jetbrains [1]. IntelliJ Struts Plugin 261.19017.1 test builds have been submitted to gather community feedback. Possible security issue reports came in and were handled with the help of the Apache Security team. No actionable issue was identified. We have no issues that require board assistance at this time. ## Community Health To keep the trends comparable, the following statistics represent data from the regular reporting quarter, cut-off at 2026-04-15. ### Development activity in the regular reporting period 20 JIRA tickets opened and 32 closed in the past quarter. We had 144 PRs opened and 141 closed in the main project. ### Mailing list activity in the regular reporting period: dev@struts.apache.org had a 6% increase in traffic in the past quarter (33 emails compared to 31) - issues@struts.apache.org had a 51% increase in traffic in the past quarter (312 emails compared to 206) - notifications@struts.apache.org had a 44% increase in traffic in the past quarter (795 emails compared to 551) - user@struts.apache.org had a 53% decrease in traffic in the past quarter (22 emails compared to 46) [1] https://lists.apache.org/thread/r7hz49l00rjc29vrwhzoy6tlkf8vzrxz [2] https://struts.apache.org/announce-2026#a20260427 ----------------------------------------- Attachment BT: Report from the Apache Subversion Project [Nathan Hartman] ## Description: The Apache Subversion® version control system exists to be universally recognized and adopted as an open-source, centralized version control solution characterized by its reliability as a safe haven for valuable data; the simplicity of its model and usage; and its ability to support the needs of a wide variety of users and projects, from individuals to large-scale enterprise operations. ## Project Status: Current project status: Ongoing, mature. Issues for the board: None at this time. ## Membership Data: Apache Subversion was founded 2010-02-16 (16 years ago). Prior to joining ASF, the project began in February of 2000 (26 years ago). There are currently 91 committers and 50 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: - Branko Čibej was added to the PMC on 2026-04-11 - Ivan Zhakov was added to the PMC on 2026-04-19 - Ivan Zhakov was added as committer on 2026-04-20 ## Project Activity: ### 1.15.0 Coming Soon The 1.15.0 release is coming soon! Release management activities have begun and the second release candidate (RC) tarball has been rolled and is currently being tested. Some issues have been identified during this testing, with fixes underway [1]. The big headliner feature for the 1.15 release line is Pristines On Demand. This feature can, at the user's option, reduce the size of checked out working copies by up to 50% by downloading pristines from the server only when needed, rather than keeping them cached locally at all times [2]. Numerous other features and improvements are coming in 1.15, including Multi-WC [3], streamy checkouts [4], and experimental support for building Subversion with CMake. For details, see the draft release notes [5] and the CHANGES file [6]. [1] https://lists.apache.org/thread/nkyhqyljkgm14cd8oqg28t193hwwydsb https://lists.apache.org/thread/cvvgmsrgz0gp6twq6tlx59s1p524mcwb https://lists.apache.org/thread/y8gkknmlqgq2xkpfk2g2c3n4nr3rb16y [2] https://s.apache.org/svn-1.15-pod [3] https://s.apache.org/svn-1.15-multiwc [4] https://s.apache.org/svn-1.15-streamy-checkouts [5] https://subversion.apache.org/docs/release-notes/1.15.html [6] https://svn.apache.org/repos/asf/subversion/trunk/CHANGES ### New Release Life Cycle There is a new life cycle and support roadmap for Subversion releases, starting with the upcoming 1.15 release line. The new roadmap is the culmination of many community discussions over several years. It aims to solve issues we encountered with the old roadmap and incorporate feedback from the wider community. The full details can be read at our Roadmap page [7]. The latest discussion thread is at [8]. [7] https://subversion.apache.org/roadmap.html#support-period [8] https://lists.apache.org/thread/gwkrrmg3qh01zmlb1wvt5vp0r5k9rsrn ### Other Activity Development of 'svnbrowse', a new Terminal User Interface (TUI) utility for browsing remote Subversion repositories. This utility should make it easier to figure out which part of a repository to checkout when working on the command line. In addition, there have been a huge number of bug fixes and code quality improvements, too numerous to list individually. ## Community Health: Activity tends to come in waves. Last summer and early autumn were noticeably quieter, but activity has increased significantly during winter 2025 and spring of this year. Two emeritus PMC members have re- joined the project; the upcoming 1.15.0 release is in progress; user questions usually receive helpful responses on the mailing lists; the codebase, website, and project infrastructure continue to be improved. Altogether, the community appears healthy for a mature and stable project. Our community is fully volunteer-driven and we would like to thank everyone for their support. ----------------------------------------- Attachment BU: Report from the Apache Superset Project [Maxime Beauchemin] ## Description: The mission of Apache Superset is the creation and maintenance of software related to data exploration, analysis, visualization, and dashboarding ## Project Status: Current project status: Ongoing, with high activity and community engagement. Issues for the board: None ## Membership Data: Apache Superset was founded 2020-11-17 (5 years ago) There are currently 77 committers and 39 PMC members in this project. The Committer-to-PMC ratio is roughly 5:3. Community changes, past quarter: - Hai Do was added to the PMC on 2026-04-10 - Gabriel Torres was added as committer on 2026-03-16 - Amin Ghadersohi was added as committer on 2026-03-20 ## Project Activity: 6.1.0 was just voted in, and is due for imminent release. 6.0.1 is also VERY close to done. MCP and Extensions projects are trucking along... and a new Kubernetes Operator. Still active and optimistic in investing in our product's future(agentic and wildly flexible/customizable). In the last 90 days * Issues opened: 260 * Issues closed: 276 * PRs opened: 1,732 * PRs merged: 1,087 * PRs closed without merging: 464 * Unique PR authors: 145 * Unique Merged PR authors: 107 * Unique issue authors: 162 Also, these seem to be slowing in growth, but still moving forward: * GitHub stars: 72,801 * Forks: 17,275 ## Community Health: Numerous conference talks are in flight... many of us are out there banging the drum! That said (as I've mentioned), only a small percentage of our roster is active, so we still intend to revisit some sort of Active vs Inactive/Emeritus roster like other projects do. Thanks for the recent guidance on this. The problem we're trying to solve is partly that of optics (giving more merit/visibility to those who actively contribute than to those who departed years ago) and also making it clear who you CAN actually ping on GitHub/Slack/Email since a lot of people gone from the project get mentioned due to git history and such, but aren't likely to respond. Getting more fly-by contributions (for better and worse) than ever (thanks, AI). We're actively trying to spot and engage with anyone who seems likely candidates for deeper involvement as Committers. Always trying to trim the issue/PR/security backlog, which seems ever-growing, and security submissions come in as fast as we can tackle them, you are probably aware. Working with other PMCs and within our own the find the most scalable ways to stay on top of everything. ----------------------------------------- Attachment BV: Report from the Apache Syncope Project [Francesco Chicchiriccò] ## Description: The mission of Syncope is the creation and maintenance of software related to Managing digital identities in enterprise environments ## Project Status: Current project status: healthy. Issues for the board: none. ## Membership Data: Apache Syncope was founded 2012-11-21 (13 years ago) There are currently 27 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 7:4. Community changes, past quarter: - No new PMC members. Last addition was Lorenzo Di Cola on 2023-05-22. - No new committers. Last addition was Alberto Bogi on 2025-11-07. ## Project Activity: Following the discussed release strategy, now that 4.1.0 was cut, we are maintaining the 4_0_X and 4_1_X branches. The master branch is hosting the next development phase. After proposal on dev@, Apache Syncope was included in the EU Open Source Solutions Catalogue: https://s.apache.org/akt21 Security: * CVE-2026-42797 * CVE-2026-42782 Recent releases: * 4.1.0-M0 was released on 2026-0-23 * 4.0.5 was released on 2026-03-31 * 4.1.0 was released on 2026-03-31 ## Community Health: The user@ mailing list traffic with questions and support requests especially from new users has recently increased, and topics seem all but trivial. This looks as a sign of actual adoption rather than initial evaluation. Discussion about planning for new releases is happening on dev@, especially about coordination with external dependencies to cope with security updates. ----------------------------------------- Attachment BW: Report from the Apache SystemDS Project [Matthias Boehm] ## Description: Apache SystemDS is a machine learning (ML) system for the end-to-end data science lifecycle from data preparation and cleaning, over efficient ML model training, to scoring and debugging. ML algorithms or pipelines are specified in a high-level language with R-like syntax, or related Python and Java APIs, and the system automatically generates hybrid runtime plans of local, in-memory operations and distributed operations on Apache Spark. ## Issues for the Board: - None ## Project Status: - Current work focuses on adding the missing primitives for a number benchmarks, a new API for the alignment of multimodal datasets (scuro), a new backend for singlenode out-of-core operations, and incremental refinements of major internal components for compression, GPUs, federated operations, and the use of the Java vector API. ## Membership Data: - Apache SystemDS was founded 2017-05-16 (incubator process entered 2015-11-02) - Last PMC members added 2026-01-07 (Christina Dionysio) - Last committers added 2026-01-07 (Jannik Lindemann, Rene Enjilian) - There are currently 39 committers and 29 PMC members in the project. ## Activity and Health: - Code activity is healthy with 49 commits (+2%) in the last 3 months. - Community growth is healthy with 20 active contributors (+53%) in the last 3 months - Communication is healthy, mailing list activity is improving, additional work on better documentation. ## Releases: - Apache SystemDS 3.3.0 was released on 2025-04-22. - Apache SystemDS 3.2.0 was released on 2024-03-17. - Apache SystemDS 3.1.0 was released on 2023-03-13. - Apache SystemDS 3.0.0 was released on 2022-06-20. - Apache SystemDS 2.2.2 was released on 2022-06-25. - Apache SystemDS 2.2.1 was released on 2021-12-02. - Apache SystemDS 2.2.0 was released on 2021-10-30. - Apache SystemDS 2.1.0 was released on 2021-06-28. - Apache SystemDS 2.0.0 was released on 2020-10-14. - Apache SystemML 1.2.0 was released on 2018-08-24. ----------------------------------------- Attachment BX: Report from the Apache Tcl Project [Georgios Petasis] ----------------------------------------- Attachment BY: Report from the Apache Tez Project [László Bodor] ## Description: Apache Tez is an effort to develop a generic application framework which can be used to process arbitrarily complex DAGs of data-processing tasks and also a re-usable set of data-processing primitives which can be used by other projects. ## Project Status: Current project status: Ongoing. Issues for the board: None. ## Membership Data: Apache Tez was founded 2014-07-16 (12 years ago) There are currently 36 committers and 33 PMC members in this project. The Committer-to-PMC ratio is roughly 1:1. Community changes, past quarter: - No new PMC members. Last addition was Ayush Saxena on 2024-09-17. - No new committers. Last addition was Ayush Saxena on 2024-01-09. ## Project Activity: Patches keep going in regarding precommit infra an cloud native initiative, which is good. ## Community Health: There is a new contributor, who's been active for months. We might consider inviting him to become a committer in a few months I believe. ----------------------------------------- Attachment BZ: Report from the Apache TomEE Project [David Blevins] ----------------------------------------- Attachment CA: Report from the Apache Traffic Server Project [Bryan Call] ## Description: The mission of Traffic Server is the creation and maintenance of a high-performance, scalable HTTP/1.1 and HTTP/2 caching proxy server that powers major CDNs worldwide. ## Project Status: Current project status: Ongoing Issues for the board: none. ## Membership Data: Apache Traffic Server was founded 2010-04-20 (16 years ago). There are currently 72 committers and 58 PMC members in this project. The Committer-to-PMC ratio is roughly 9:8. Community changes, past quarter: - No new PMC members. Last addition was Mo Chen on 2024-04-15. - Jake Champion was added as a committer on 2026-04-06. ## Project Activity: Notable work this quarter includes shipping the ssl_multicert configuration in YAML form, parallelizing SSL certificate load at startup, adding a ja4_fingerprint plugin with BoringSSL support and a new jax_fingerprint plugin, adding a filter_body plugin for request and response body content filtering, adding Cache Groups concepts to Cripts, implementing RFC 9213 Targeted HTTP Cache Control with a CDN-Cache-Control default, ignoring malformed Cache-Control directives per RFC 7234, adding Lua plugin support for the connection exempt list, fixing cache directory corruption in parallel directory sync, and adding a parallel autest runner that materially reduces CI time. We also did substantial portability and TLS library work, including a fix to build with OpenSSL 3.5+ after the engine API was removed, additional BoringSSL compatibility, OCSP stapling crash and timeout hardening, and making the 9.2.x branch build on macOS 26. Development remains healthy with 20 active contributors merging 256 pull requests across 174 commits to master. The project closed more issues than were opened (66 closed vs. 51 created), continuing to reduce our backlog. We shipped four bug fix releases this quarter: 9.2.12 and 10.1.1 on February 6, followed by 9.2.13 and 10.1.2 on April 2-3. Work on the next feature release, 10.2.0, is underway on the 10.2.x branch. ATS 11.0.0 remains targeted for late summer. ## Community Health: We are holding a virtual ATS Summit on May 20-21, 2026, two remote half-days. Planned topics include the state of the project, the ATS 11 roadmap, AI-assisted code review and development workflows, CI and testing improvements, and documentation and onboarding. We continue to hold weekly bug and issue scrubs every Monday, ensuring timely review of pull requests and resolution of user-reported issues. The project continues to close more issues than are opened, indicating good maintenance of the codebase. There is active participation in code reviews and discussions on the dev mailing list. ----------------------------------------- Attachment CB: Report from the Apache TsFile Project [Jialin Qiao] ## Description: The mission of Apache TsFile is the creation and maintenance of software related to a columnar storage file format designed for time series data ## Project Status: Current project status: Ongoing with high activity. Issues for the board: No. ## Membership Data: Apache TsFile was founded 2023-11-15 (2 years ago) There are currently 21 committers and 18 PMC members in this project. The Committer-to-PMC ratio is 7:6. Community changes, past quarter: - No new PMC members. Last addition was Gaofei Cao on 2023-11-15. - No new committers. Last addition was Xinhao Gu on 2025-04-22. ## Project Activity: ### Recent releases: - 2.3.0 was released on 2026-04-27. - 2.2.1 was released on 2026-03-20. - 2.2.0 was released on 2025-12-30. ### Main work of project: This quarter saw significant progress in both feature development and multi-language ecosystem expansion. The tag filter feature, which enables filtering conditions on tag columns, has been completed. We also added support for importing data from Apache Parquet and Apache Arrow formats into TsFile, allowing users to convert existing columnar datasets into TsFile format with schema mapping or automatic inference. On the Python side, TsFileDataFrame was introduced, enabling users to read TsFile data directly as Pandas DataFrames. Python wheel support has been extended to Python 3.14, and compatibility with a broader range of NumPy versions has been improved. ## Community Health: dev@tsfile.apache.org had a 54% decrease in traffic in the past quarter (35 emails compared to 76). The decline is mainly because development this quarter was execution-focused — implementing features previously discussed on the mailing list — and more day-to-day discussions are happening on GitHub pull requests and issues. We are currently in contact with the Hugging Face community, working to make TsFile a first-class citizen in Hugging Face Datasets for storing time-series modality data. A pull request[1] has been submitted and is under review. [1] https://github.com/huggingface/datasets/pull/8160 ----------------------------------------- Attachment CC: Report from the Apache Turbine Project [Georg Kallidis] ## Description: The mission of Turbine is the creation and maintenance of software related to A Java Servlet Web Application Framework and associated component library ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Turbine was founded 2007-05-16 (19 years ago) There are currently 12 committers and 9 PMC members in this project. The Committer-to-PMC ratio is 4:3. Community changes, past quarter: - No new PMC members. Last addition was Jeffery Painter on 2017-11-12. - No new committers. Last addition was Youngho on 2021-12-06. ## Project Activity: The project is now ready for preparing a next release cycle probably in v8.0 with Java baseline 21 or later - yet with currently overall low code activity. Fulcrum parser, which is designed to be used extensively in velocity templates, does now allow sub classes to implement custom filtering of parameters as a security measure. Besides this, other smaller code changes in components are mainly house keeping (skins, dependencies, ..). ## Community Health: Turbine developer community has currently not yet decided in the mailing list, which way to go, but security issues and an Java upgrade are already the major issues to be considered. More topics on the ASF level like trusted releases and responsible AI absorb attention, although without current impact on the project. ----------------------------------------- Attachment CD: Report from the Apache Uniffle Project [He Qi] Description: The mission of Apache Uniffle is the creation and maintenance of software related to a unified remote shuffle service Project Status: Current project status: Ongoing Issues for the board: None Membership Data: Apache Uniffle was founded 2025-02-19 (a year ago) There are currently 24 committers and 14 PMC members in this project. The Committer-to-PMC ratio is roughly 3:2. Community changes, past quarter: No new PMC members. Last addition was Xianjing Feng on 2025-05-07. No new committers. Last addition was Lu Yuan on 2025-04-10. Project Activity: The community is supporting Spark 4.1. Users will benefit for Spark 4.1 and Uniffle at the same time. The work is really promising. Production stability is also important. The community has fixed some bugs which make the job hanging all the time. The performance is still optimzed for the production environment. Community Health: Overall community health is good. The community is stable. The community developers are fixing the issues reported by users. The new features are developing expecially for Spark 4.1 support. The automation release is also discussing. ----------------------------------------- Attachment CE: Report from the Apache Velocity Project [Nathan Bubna] ## Description: The mission of Velocity is the creation and maintenance of software related to A Java Templating Engine ## Project Status: Current project status: Ongoing Issues for the board: none ## Membership Data: Apache Velocity was founded 2006-10-24 (20 years ago) There are currently 16 committers and 10 PMC members in this project. The Committer-to-PMC ratio is 8:5. Community changes, past quarter: - Claude Warren was added to the PMC on 2026-04-12 - Claude Warren was added as committer on 2026-04-13 ## Project Activity: On 2026-04-18, the Velocity Master POM 8 release was promoted. We are gearing up for new Engine and Tools releases, but of course, at our usual volunteer, plodding pace. ## Community Health: The addition of a new PMC member/committer is nice. Contributions are slow, and reactions to those are slow as well, but we're solid and healthy enough considering the completeness of the libraries. A lot of the work we're slowly doing is simply reacting to environmental changes like the jakarta namespace. ----------------------------------------- Attachment CF: Report from the Apache Web Services Project [Daniel Kulp] ----------------------------------------- Attachment CG: Report from the Apache Whimsy Project [Dave Fisher] ## Description: The mission of Apache Whimsy is the creation and maintenance of software related to tools that help automate various administrative tasks or information lookup activities ## Project Status: - Current project status: Dormant / maintenance - Issues for the board: None ## Membership Data: Apache Whimsy was founded 2015-05-19 (11 years ago) There are currently 13 committers and 11 PMC members in this project. The Committer-to-PMC ratio is roughly 7:6. Community changes, past quarter: - No new PMC members. Last addition was Dave Fisher on 2025-07-15. - No new committers. Last addition was Dave Fisher on 2025-07-16. ## Project Activity: Maintenance only. Mostly occurs in the Secretary's workbench. ## Community Health: There is really no community development since this is a non-releasing community that is not adding new features. ----------------------------------------- Attachment CH: Report from the Apache Xalan Project [Gary D. Gregory] ## Description: Apache Xalan exists to promote the use of XSLT. We view XSLT (Extensible Stylesheet Language Transformations) as a compelling paradigm that transforms XML documents, thereby facilitating the exchange, transformation, and presentation of knowledge. The ability to transform XML documents into usable information has great potential to improve the functionality and use of information systems. We intend to build freely available XSLT processing components in order to engender such improvements. ## Project Status: Current project status: Ongoing with low activity. Issues for the board: None. ## Membership Data: Apache Xalan was founded 2004-09-30 (22 years ago) There are currently 57 committers and 5 PMC members in this project. The Committer-to-PMC ratio is roughly 8:1. Community changes, past quarter: - No new PMC members. Last addition was Joseph Kessselman on 2023-08-07. - No new committers. Last addition was Joseph Kessselman on 2023-06-29. ## Project Activity: The main activity for this reporting period is the release of an Alpha-1 to introduce support for XSLT 3.0. Ongoing work is in progress toward an Alpha-2. There is no activity on the C side of the house. ## Community Health: While email traffic is up this is likely a result of Jira traffic and discussion of XSLT 3.0 Alpha work. There is no new contributor and the overall project aside from XSLT 3 is quiet on the Java and C side. ----------------------------------------- Attachment CI: Report from the Apache Xerces Project [Michael Glavassevich] ----------------------------------------- Attachment CJ: Report from the Apache XML Graphics Project [Clay Leeds] ## Description: Apache XML Graphics exists to promote the use of XML. We view XML as a compelling paradigm that structures data as information, thereby facilitating the exchange, transformation, and presentation of knowledge. The ability to transform raw data into usable information has great potential to improve the functionality and use of information systems. We intend to build freely available products for the conversion of XML to graphical output and closely related technologies in order to engender such improvements. ## Project Status: Current project status: * No new releases since the last Board Report Issues for the board: We are still working to resolve a trademark issue for FOP was identified related to a NuGet package name[1] and we are working through resolution with help from trademarks@. [1] FOP.dll 1.1.0 https://www.nuget.org/packages/FOP.dll ## Membership Data: Apache XML Graphics was founded 2004-10-19 (22 years ago) There are currently 22 committers and 12 PMC members in this project. The Committer-to-PMC ratio is 2:1. The latest versions of Apache XML Graphics Project subprojects were released 2025-05-06: * Apache Batik 1.19 * Apache FOP 2.11 * Apache FOP PDF Images 2.11 * Apache XML Graphics Commons 2.11 ## Community changes, past quarter: * New PMC member Joao Andre Goncalves added 2026-04-08. * No new committers. Last addition was Joao Goncalves on 2024-11-12. ## Project Activity: * Latest versions are Apache Batik 1.19, Apache FOP 2.11, Apache FOP PDF Images 2.11 and Apache XML Graphics Commons 2.11 * All XMLGraphics project repositories have been migrated from Subversion to GitHub/GitBox: https://github.com/apache/xmlgraphics-fop.git * A proposal to migrate XMLGraphics projects from Jira to GitHub issues was passed. Preliminary work to effect this migration has started. The migration is ongoing. Latest Versions of Apache XML Graphics Project Sub Projects: * Apache Batik 1.19 2025-05-06 * Apache FOP 2.11 released 2025-05-06 * Apache FOP PDF Images 2.11 released 2025-05-06 * Apache XML Graphics Commons 2.11 released 2025-05-06 We have migrated the Apache XML Graphics repositories for Apache XML Graphics Commons, FOP, FOP PDF Images and Batik to GitHub: https://github.com/apache/xmlgraphics-commons.git https://github.com/apache/xmlgraphics-fop.git https://github.com/apache/xmlgraphics-fop-pdf-images.git https://github.com/apache/xmlgraphics-batik.git ## Community Health: The level of community and developer activity remains at a consistent, moderate, level with respect to the previous reporting period. ----------------------------------------- Attachment CK: Report from the Apache YuniKorn Project [Wilfred Spiegelenburg] ## Description: The mission of Apache YuniKorn is the creation and maintenance of software related to a standalone resource scheduler responsible for scheduling batch jobs and long-running services on large scale distributed systems running in on-premises environments as well as different public clouds ## Project Status: Current project status: Ongoing, with high activity. Issues for the board: none ## Membership Data: Apache YuniKorn was founded 2022-03-16 (4 years ago) There are currently 39 committers and 29 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Chia-Ping Tsai on 2024-03-07. - No new committers. Last addition was Mit Desai on 2025-11-12. ## Project Activity: Recent releases: 1.8.0 was released on 2026-02-04. 1.7.0 was released on 2025-07-28. 1.6.3 was released on 2025-05-06. Development work on 1.9.0 is ongoing with a beta release expected by late May 2026. ## Community Health: 11 new jira account created. 54 new Jiras created and 37 resolved, with corresponding GitHub PRs: 82 created and 80 resolved. The 1.8.0 release was finalised and released a couple of days later than expected. Development of the 1.9.0 is progressing well with the major change, plugin removal, in the final stages. The plugin rdeployment emoval change is a long term roadmap item. Based on the current planning the beta for 1.9.0 is planned for late May with the release planned for June. ------------------------------------------------------ End of minutes for the May 20, 2026 board meeting.