What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
| Date | Action | Decided by |
|---|---|---|
| 2026-02-18 | Appointed Jean-Baptiste Onofré | the board, by resolution |
| Date | Decision | Item | Outcome |
|---|---|---|---|
| 2026-02-18 | Establish the Apache Polaris Project | special order | approved |
## 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: Healthy and active. This is Apache Polaris's first quarterly board report, following the initial monthly reports filed after the project graduated to a Top-Level Project on 2026-02-18. The transition out of incubation has been smooth: the project has established and sustained a monthly release cadence, the PMC is operating independently and in the Apache Way, development activity remains high, and several substantial feature proposals are under active discussion on the dev list. Compared with the previous report(s): the most notable change is the shift from monthly to quarterly reporting itself, marking the project's settling into a normal TLP rhythm. The release train established immediately post-graduation has continued without slippage (two feature releases plus a patch this period). The character of activity has also evolved (where the earlier reports centered on the graduation transition and post-graduation stabilization), this quarter the community has moved toward expanding the catalog's scope, with major design proposals (Data Sharing, OpenLineage, Polaris Directory) now under active discussion. Committer growth continued with one addition. Issues for the board: None ## Membership Data: Apache Polaris was founded 2026-02-18 (5 months ago) There are currently 32 committers and 19 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 Sung Yun on 2026-04-27. - Nándor Kollár was added as committer on 2026-06-30 ## Project Activity: The project maintained its monthly release cadence throughout the quarter, continuing the train established right after graduation: - 1.6.0 released 2026-07-08 - 1.5.0 released 2026-05-18 - (1.4.1, a patch release, shipped 2026-05-01 at the start of the period) Development throughput on GitHub (apache/polaris) remained high over the reporting window (May–July 2026): - Pull requests: 761 opened, 651 merged - Issues: 90 opened, 91 closed - Currently open: 102 pull requests, 256 issues The high merge count relative to issues reflects a fast-moving, PR-driven workflow with a healthy review throughput. Recent release work has focused on hardening the project for production use, including running event listeners on a dedicated configurable executor, an updated MaintenanceService API, and stricter REST-layer validation of entity names. Broader ongoing themes include catalog federation, credential vending, and governance/policy integration. Several notable feature proposals and design discussions are active on the dev list this quarter, reflecting a shift from stabilization toward expanding the catalog's scope: - Data Sharing / Catalog Sharing: a design for securely sharing catalog namespaces and tables (metadata pointers) with external accounts and partner engines without copying data, including recipient credentials and revocation. - OpenLineage: a sustained proposal thread exploring how Polaris should emit and integrate lineage information, positioning the catalog as a lineage/ observability plane. This pairs with related discussions on REST endpoints exposing table metrics and events. - Polaris Directory: a proposal for a directory/volume-style abstraction to organize files and unstructured data within the catalog, extending Polaris beyond Iceberg tables toward broader data-asset management. - Polaris Semantic: we are discussing how to "integrate" Apache Ossie (incubating) in Polaris and the concrete valuable use cases. - Polaris Tagging: it has been discussed quickly last year, it's now back in discussion. The purpose is to be able tag Polaris entities to facilitate the discover and usage. Release voting, discussion, and decision-making continue to take place on the public dev@ list in accordance with the Apache Way. ## Community Health: Community health is good. Development is broadly distributed: 58 distinct authors opened pull requests against apache/polaris during the quarter, a strong contributor-diversity signal for a project only a few months past graduation. The project added one new committer this quarter (Nándor Kollár, 2026-06-30), reflecting continued growth of the contributor base on merit. The committer and PMC rolls remain diverse, spanning multiple cloud providers, engine and governance vendors, and independent contributors, which keeps the project vendor-neutral and resilient to any single contributor's departure. The volume and substance of design discussion on the dev list (spanning data sharing, lineage, and unstructured-data support) indicates an engaged community debating the project's direction openly. There were no new PMC members this quarter; the PMC will continue to watch for sustained contributors who are candidates for invitation.
## 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.
## 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 (post graduation) Issues for the board: None ## Membership Data: Apache Polaris was founded 2026-02-18 (a month ago) There are currently 31 committers and 18 PMC members in this project. The Committer-to-PMC ratio is roughly 8:5. Community changes, past quarter: - No new PMC members (project graduated recently). - 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: * Release 1.4.0 Preparation: Development began on the first post-graduation release. Key focus areas include updating LICENSE/NOTICE files to reflect TLP status and adding new artifacts, such as the Python CLI. * Release Catalog Migrator 1.0.0: A new tool, the Catalog Migrator, has been released. This utility is critical for users looking to migrate existing metadata from Hive or AWS Glue catalogs into Polaris. * Polaris Authorizer Refactoring: Significant progress was made on enhancing the PolarisAuthorizer. A major PR reached consensus to improve how the catalog handles authorization for external engines. * Feature Graduation: The "Generic Table" capability officially graduated from beta. This allows Polaris to manage metadata for formats beyond Iceberg, specifically providing stable support for Apache Hudi and Delta Lake. * Credential Vending: New PR activity focused on refining AWS IAM AssumeRole flows and expanding storage-scoped credentials to improve security in multi-tenant environments. Also preparation for Credential Vending support in Generic Table started. ## Community Health: * New Members: The project welcomed three new committers this month: Adam Christian, Adnan Hemani, Danica Fine, and Christopher Lambert. * Community Syncs: Two major community meetings were held (March 5 and March 19). Discussions centered on the roadmap for the new Security features (Apache Ranger support, refactoring of the Polaris Authorizer, ...), Polaris Events, Polaris Console (UI). * New Communication Channels: The community launched an official YouTube channel (@ApachePolaris) to host recordings of community meetings and technical deep dives, making project updates more accessible to a global audience. * Event Planning: Preparation is underway for Iceberg Summit 2026 (April 8–9), where several talks about Polaris will happen (https://www.icebergsummit.org/). Also, Polaris Community Sprint on the afternoon of April 7th (https://luma.com/q8w8v7as).
## 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 (recently graduated)
Issues for the board: None
## Membership Data:
Apache Polaris was founded 2026-02-18 (20 days ago)
There are currently 30 committers and 18 PMC members in this project.
The Committer-to-PMC ratio is 5:3.
Community changes, past quarter:
- No new PMC members (project graduated recently).
- Adam Christian was added as committer on 2026-03-07
- Adnan Hemani was added as committer on 2026-03-07
- Danica Fine was added as committer on 2026-02-27
## Project Activity:
* Releases:
- Work began on Apache Polaris 1.4.0, the first release under the new TLP
status. This release prep is a bit longer, as it needs updates on
LICENSE/NOTICE, including new artifacts (like Python CLI).
- Catalog Migrator 1.0.0 (RC2): A critical tool for migrating tables from
Glue/Hive to Polaris entered its final voting stage in early March.
- We will also consider releases for new tools soon (Polaris Console, Polaris
MCP server, ...)
* Technical Roadmap & Feature Development: Following the successful 1.3.0
release in mid-January, the development team shifted focus toward enterprise
hardening and interoperability.
- Scan Metrics Persistence: A major architectural effort is underway to
integrate query scan metrics into the catalog, enabling better observability
for downstream engines like Spark and Trino.
- Credential Vending Enhancements: Significant PR activity has focused on
refining AWS IAM AssumeRole flows and expanding support for storage-scoped
credentials, reducing security overhead for multi-tenant data lakes.
- Generic Table Stability: The "Generic Table" feature officially graduated
from beta. This allows Polaris to manage metadata for Delta Lake and Apache
Hudi tables alongside Iceberg, positioning it as a universal catalog.
* Governance & Graduation Infrastructure The transition to a TLP required
significant "Project Hygiene" to ensure compliance with the Apache Way:
- Release Process Modernization: The community moved to a unified CI/CD
pipeline, merging six disparate workflows into one. This has stabilized the
build process and automated the generation of convenience binaries and
Docker images.
- Legal & Licensing: Conducted a comprehensive audit of all dependencies.
Resolved a key legal blocker regarding third-party library nesting to ensure
the upcoming 1.4.0 release (the first as a TLP) is fully compliant.
* Ecosystem Integration
- Engine Support: Verified compatibility and performance benchmarks for the
latest versions of Apache Doris and StarRocks, which now use Polaris as
their default external Iceberg catalog.
- Community Engagement: Recorded high attendance at the February 19th
community sync, where the transition to TLP was celebrated and the 2026
roadmap—including AI/ML metadata extensions—was first socialized.
## Community Health:
* Governance Independence The project has achieved a high level of
organizational maturity and is no longer reliant on its founding
contributors.
- Diverse PMC: The Project Management Committee (PMC) now includes 13 members
representing seven different organizations, including Dremio, Snowflake,
Databricks, Microsoft, Confluent, LanceDB, Red Panda.
- Organic Leadership: Of the current PMC, 46% (6 members) were elected during
the incubation period based on their merit and contributions, rather than
being part of the initial donation. Similarly, 5 out of 8 current committers
were promoted from within the community during incubation.
* Engagement & Outreach Metrics (Feb – March 2026) The "graduation window" saw
a spike in community engagement, particularly from new enterprise adopters.
- Contributor Growth: The project surpassed the 100-contributor milestone in
February. Since the end of January, 13 new individual contributors have had
their first pull requests merged.
- Mailing List Activity: The dev@ mailing list saw a 25% increase in traffic
during February, focused on TLP transition logistics, the 1.4.0 roadmap, and
the resolution of legal hygiene tasks.
- Meetups:
* Warsaw (Feb 18): A community-led meetup focused on Iceberg V4 and Polaris
performance.
* Redmond (Feb 26): Hosted by Microsoft, focusing on Polaris integration
within the Azure/Fabric ecosystem.
* Participation Quality Unlike many projects that see "drive-by"
contributions, Polaris has seen a rise in "deep" technical participation:
- Feature Design: Significant community-led design discussions occurred in
February regarding Scan Metrics Persistence and ExternalCatalogFactory
refactoring.
- Integration Support: Third-party projects like Apache Doris, StarRocks, and
Fivetran have integrated Polaris as their default Iceberg REST catalog,
contributing back stability fixes and performance optimizations.
* Documentation & Onboarding To ensure continued health, the community has
prioritized "contributor experience":
- Unified CI/CD: A major effort in February consolidated several disparate CI
pipelines, reducing PR feedback loops and making it easier for new
developers to verify their work.
- Blog & Roadmap: The project launched several technical blogs in early 2026,
including guides on policy-driven table maintenance and AI-native storage
integration with LanceDB.
Polaris is 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. Polaris has been incubating since 2024-08-09. ### Three most important unfinished issues to address before graduating: 1. Check the Polaris existing trademarks at the ASF (transfer has been done, to be verified) 2. Perform a namesearch (for the record as previous point) ### 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? Between 2025-07-31 and 2025-10-31: - 2 new releases - 17 new contributors - 649 PRs opened / 517 PR merged - 745 messages on the dev@ mailing list We are happy to see new contributors who contributed important new features: - OPA support. - Polaris Console (UI) is coming. - S3 KMS support. ### How has the project developed since the last report? We did 1.1.0-incubating and 1.2.0-incubating releases since the last report. 1.3.0-incubating release is also in preparation. Here's the highlights about project development since the last report: - Improvement on the website, adding new blog posts (StarRocks and Polaris integration) - Moving forward on NoSQL support - New OPA Authorizer - New MetricsReport interface - New JDBC schema evolution support - A lot of improvements on Python (CLI, ...) - Enhanced support for S3-compatible (on-prem) storage - Automated release workflows are in place, ongoing work to support ATR - Apache Polaris website is now integrated to analytics.apache.org ### 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 - [X] Nearing graduation - [ ] Other: ### Date of last release: 2025-10-27 ### When were the last committers or PPMC members elected? Last PPMC member has been elected on 2025-11-19 (Yong Zheng). ### Have your mentors been helpful and responsive? Mentors are helpful and responsive. ### Is the PPMC managing the podling's brand / trademarks? Yes, the podling manages the brand/trademarks, especially working with 3rd parties organizing meetups. ### Signed-off-by: - [ ] (polaris) Holden Karau Comments: - [ ] (polaris) Kent Yao Comments: - [ ] (polaris) Ryan Blue Comments: - [X] (polaris) Jean-Baptiste Onofré Comments: Again a solid activity on the podling, I can see new contributors and consistent interest. Maybe the podling should consider starting discussion about graduation soon? - [X] (polaris) François Papon Comments: As new mentor, I can see a lot of dicussion on the mailing list, the community looks to be safe and growing. The project has released several version and it's closed to the graduation. ### IPMC/Shepherd notes:
Polaris is 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. Polaris has been incubating since 2024-08-09. ### Three most important unfinished issues to address before graduating: 1. Review maturity model ### 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? Regarding the user community: * On Slack, we note an increase of 7% of the number of messages (with a peak of 580 messages during last month). These Slack messages happen 77% on public channels and 21% as direct messages (which is a good ratio). NB: we are using the free plan for Slack, meaning that the messages retention is 90 days. It's interesting to note that we got messages from 21 threads started by new Slack users. * On GitHub Issues, we had 19 issues created by new users. * On the dev mailing list, we had 196 messages in August, 278 messages in July, and 311 messages in June. Regarding the dev community: * We had 46 Pull Requests from 13 new contributors * Community meetings happened on 2025-06-12, 2025-06-26, 2025-07-24, 2025-08-28, all recorded and shared publicly (on the dev mailing list and the website, see https://polaris.apache.org/community/meetings/) We participated in events to promote Apache Polaris: * Apache Beam Summit 25 New York City * Apache Iceberg Meetup Paris June 25 * Snowflake Summit SF June 25 * Data and AI - Lakehouse MiniSummit SF June 25 ### How has the project developed since the last report? We released 1.0.0-incubating, which is an important milestone for the podling: * Binary distributions (.tgz/.zip) and Docker images * Official Helm chart for Kubernetes * Quarkus runtime for fast startup * Policy store with built-in data TMS policies * Rollback compaction on conflicts * 3rd Party IdP integration * Federation and generic table support (experimental) We also released 1.0.1-incubating, mostly to fix an issue on the Helm chart. In order to faster ship fixes and new features, we agreed about a monthly release cadence. We are also discussing several proposals: * Table Source * Client/Authentication API * Event API * Async & Reliable Tasks * Commit Deconfliction * Row and Column Based Access Control * S3 Remote Signing * FGAC * ... ### 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 - [X] Nearing graduation - [ ] Other: ### Date of last release: 2025-08-16 ### When were the last committers or PPMC members elected? Last committers: Yun Zou elected on 2025-06-08 Last PPMC members: Dmitri Bourlatchkov, Dennis Huo, Yufei Gu elected on 2025-03-25 ### Have your mentors been helpful and responsive? Yes, helpful in releases review mostly. ### Is the PPMC managing the podling's brand / trademarks? Polaris PPMC is working with 3rd parties willing to use Polaris brand/trademarks, according to https://incubator.apache.org/guides/publicity.html and https://incubator.apache.org/guides/branding.html. ### Signed-off-by: - [ ] (polaris) Bertrand Delacretaz Comments: - [ ] (polaris) Holden Karau Comments: - [X] (polaris) Kent Yao Comments: The community is very active in project developing, delivering releases and community building. - [X] (polaris) Ryan Blue Comments: Good progress on the project. I think that the community is getting more used to the Apache Way but still needs guidance. This is based on uncertainty about when to use the private list and when to use a vote (vs asking for further discussion). - [X] (polaris) JB Onofre Comments: I'm happy to see new contributors and people active in the Polaris community. Also the podling did good progress on the releases front. ### IPMC/Shepherd notes:
Polaris is 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. Polaris has been incubating since 2024-08-09. ### Three most important unfinished issues to address before graduating: 1. Finalize "complete" release (including binary distributions and artifacts), and adopt regular releases pace 2. Grow the community 3. Fill out the maturity model ### 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? Regarding the user community: * On Slack, since March, we have 17 threads from new users (28 new users in May, 53 new users in April, 53 new users in March) * On GitHub Issues, we had 11 new issues created by new users. * On the dev mailing list, we had 196 messages in March, 144 in April, 279 in May, mostly from Polaris committers/contributors. It seems the users prefer to ask questions on Slack. Regarding the dev community: * We had 7 Pull Requests from 7 new contributors * We are discussing with the Apache XTable community (for multi table formats support) * Community meetings happened on 2025-04-03 and 2025-04-17 (recorded and publicly available) In order to build/grow the Polaris community, we participated to different events (meetups, etc) to introduce Apache Polaris: * Open Source Data Deep Dive: London (2025-05-21) * Current 25 London (2025-05-20) * Open Source Data Deep Dive: Barcelona (2025-05-15) * Munich Database Meetup: Analytics Data Stack (2025-05-13) ### How has the project developed since the last report? We added the polaris-tools repo (https://github.com/apache/polaris-tools) to host parts of the project (benchmark tool, catalogs migrator, ...) not directly related to the Polaris "catalog server". Highlights in the project developed: * We refactored the persistence layer to use pure JDBC now and we deprecated EclipseLink use. * We are working on gather server and tool in an unique distribution * Several proposals are in discussion right now (event/observe API, async tasks, spark client, ...) In preparation for 1.0-incubating release, we are voting 0.10-incubating release. We are focusing on 1.0-incubating release, the release process should start quickly after 0.10-incubating release vote pass. ### 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-02-25 ### When were the last committers or PPMC members elected? Last committers: Ajantha Bhat, Pierre Laporte, Prashant Singh, Jonas Jiang elected on 2025-04-30 Last PPMC members: Dmitri Bourlatchkov, Dennis Huo, Yufei Gu elected on 2025-03-25 ### Have your mentors been helpful and responsive? Yes, helpful in releases review and reporting issues. ### Is the PPMC managing the podling's brand / trademarks? Polaris PPMC is working with 3rd parties willing to use Polaris brand/trademarks, according to https://incubator.apache.org/guides/publicity.html and https://incubator.apache.org/guides/branding.html. ### Signed-off-by: - [ ] (polaris) Bertrand Delacretaz Comments: - [ ] (polaris) Holden Karau Comments: - [X] (polaris) Kent Yao Comments: LGTM - [ ] (polaris) Ryan Blue Comments: - [X] (polaris) JB Onofré Comments: ### IPMC/Shepherd notes:
Polaris is 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. Polaris has been incubating since 2024-08-09. ### Three most important unfinished issues to address before graduating: 1. Prepare 1.0.0 release including binary distribution 2. Grow the community ### 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? Regarding the users community: - on Slack (#general channel), in February, we had questions from 11 new users, evaluating Polaris. These users are not active on the dev mailing list (only Slack). - on GitHub Issues, in February, we had 2 new issues created by non committers users, and non affiliated to initial committed companies. Some users are the same active on Slack (for instance https://github.com/apache/polaris/issues/996) Regarding the contributors community: - in February, we had 7 PRs from 5 new contributors (individual contributors, not affiliated to companies already active in Polaris) - in February, we had several GitHub issues and PRs created by 3 new contributors from Snowflake and a new contributor from Dremio. In February, we had several Community Meetings (recorded and shared on the dev mailing list and website): - 2 Polaris Community Meetings - Discussion about the Policy Management proposal - Discussion about Polaris Persistence improvement proposal On these meetings, we were pleased to see several new people (around 15 people show up for the first time in February). We continue to promote Polaris in order to grow our community. We strongly believe 1.0.0 release (with the binary distributions) will help to grow even faster our community. ### How has the project developed since the last report? 0.9.0 has been released. This release is the first one on the project, only including source distribution. We are now working on 1.0.0 release that will include binary distributions. We published a roadmap proposal (https://github.com/apache/polaris/discussions/1028), and we added a 1.0-blocker label on GH Issues. In February, we had 3 new proposals in discussion (relayed on the dev mailing list): - Persistence layer improvement (https://github.com/apache/polaris/issues/985) - Policy Management (https://github.com/apache/polaris/issues/999) - Generic Table Support (https://github.com/apache/polaris/issues/1048) We are now focusing on 1.0.0 preparation, including fixes and the persistence layer improvement. ### 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-02-25 ### When were the last committers or PPMC members elected? Last committer: Dennis Huo and Dmitri Bourlatchkov elected on 2024-12-23 ### Have your mentors been helpful and responsive? Yes, helpful in release and report review. ### Is the PPMC managing the podling's brand / trademarks? Polaris PPMC is working with 3rd parties willing to use Polaris brand/trademarks, according to https://incubator.apache.org/guides/publicity.html and https://incubator.apache.org/guides/branding.html. ### Signed-off-by: - [ ] (polaris) Bertrand Delacretaz Comments: - [ ] (polaris) Holden Karau Comments: - [ ] (polaris) Kent Yao Comments: - [X] (polaris) Ryan Blue Comments: I think "working towards first release" can be unchecked. Thanks for the additional detail on community growth! - [X] (polaris) JB Onofre Comments: I'm looking forward 1.0.0 release ! ### IPMC/Shepherd notes:
Polaris is 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. Polaris has been incubating since 2024-08-09. ### Three most important unfinished issues to address before graduating: 1. Finalize the first 0.9.0 release 2. Grow the community, especially in terms of contributors 3. Following 0.9.0 release, we are heading to 1.0.0 that will be a larger release, including binary distributions. ### 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? - All discussions (design proposals, process improvements) are discussed on the mailing list (94 messages on the dev mailing in Dec 24, 196 in Jan 25 for instance) - New users showed on Slack: - New contributors interested to work on key features for Polaris (2 expressed interest for storage backend and TMS) - Two new committers have been elected during the last quarter (Dmitri Bourlatchkov, Dennis Huo) ### How has the project developed since the last report? We are working on a lot of important changes for the project, allowing Polaris to support more use case (especially storage backends). We also have discussions about new features: Table Maintenance Policy, Federated Catalogs, ... (on the mailing list with the GitHub Issues for tracking). ### How would you assess the podling's maturity? Please feel free to add your own commentary. - [ ] 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? New committers have been elected on Jan 13, 2025. ### Have your mentors been helpful and responsive? Yes, a lot of help for LICENSE/NOTICE fixes. ### Is the PPMC managing the podling's brand / trademarks? Yes ### Signed-off-by: - [ ] (polaris) Bertrand Delacretaz Comments: - [ ] (polaris) Holden Karau Comments: - [ ] (polaris) Kent Yao Comments: - [X] (polaris) Ryan Blue Comments: Fixed some formatting in the report. For community development, are there more specific data points (other than "more")? How many contributions are coming from contributors outside of the original set of contributors and companies? In these reports, try to focus more on community growth and development than project development. - [X] (polaris) JB Onofre Comments: ### IPMC/Shepherd notes:
Polaris is 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. Polaris has been incubating since 2024-08-09. ### Three most important unfinished issues to address before graduating: 1. Prepare the first release 2. Grow the community 3. Promote the project (blogs, events, ...) ### 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? Polaris already promoted new committers this month. We see a lot of interest in Polaris, and adoption seems promising. ### How has the project developed since the last report? Polaris already promoted new committers this month. We see a lot of interest in Polaris, and adoption seems promising. We had several events (Chill Data Summit London, Big Data London, CoC NA, ...), webinar, blog posts and articles promoting Apache Polaris (incubating). The website has been published, now powered by Hugo to easily manage versioned documentation. ### 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? New committers have been elected this month: * Anna Filippova * Eric Maynard * Michael Collado * Yufei Gu * Yuya Ebihara ### Have your mentors been helpful and responsive? Yes ### Is the PPMC managing the podling's brand / trademarks? All brand usage (or plan to use) is going via the PPMC with support of markpub@apache.org and VP trademark. ### Signed-off-by: - [ ] (polaris) Bertrand Delacretaz Comments: - [ ] (polaris) Holden Karau Comments: - [ ] (polaris) Kent Yao Comments: - [X] (polaris) Ryan Blue Comments: I'm glad to see the list of new committers! That's great news given how long the project has been active, but it indicates that perhaps there's something to report in the report section "How has the project developed since the last report"? Perhaps that's an oversight. - [X] (polaris) JB Onofre Comments: ### IPMC/Shepherd notes: