LGTM

On Tue, Sep 15, 2026 at 10:48 AM Ryan Blue <[email protected]> wrote:

> Hey everyone,
>
> Our September board report is due. Sorry I’m a bit late this quarter.
>
> For this report, I’ve switched to summarizing the community’s releases and
> spec changes rather than using the highlights from our community syncs.
> That’s because there are always more and more highlights to report! I think
> this is going to be a better strategy since it reports what is actually
> available, not just in progress. Another benefit is that this is easier to
> compile and will force us to post good release highlights in the vote,
> result, or announce emails.
>
> I went ahead and reviewed release notes for the release that didn’t have
> highlights, but next time I’ll probably just note that a release happened —
> so please take the time to draw attention to the high level improvements in
> releases.
>
> The draft is below. Thanks, for all the hard work and awesome
> improvements, everyone!
>
> Ryan
> Description:
>
> Apache Iceberg is a table format for huge analytic datasets that is
> designed
> for high performance and ease of use.
> Project Status:
>
> Current project status: Ongoing
> Issues for the board: None
> Membership Data:
>
> Apache Iceberg was founded 2020-05-19 (6 years ago)
> There are currently 40 committers and 25 PMC members in this project.
> The Committer-to-PMC ratio is 8:5.
>
> Community changes, past quarter:
>
>    - No new PMC members. Last addition was Prashant Singh on 2026-02-23.
>    - Maximilian Michels was added as committer on 2026-07-25
>
> Project Activity:
>
> Releases:
>
>    - Terraform Provider 0.1.0 was released on 2026-09-02
>    - PyIceberg 0.12.0 was released on 2026-08-31
>    - Rust 0.10.1 was released on 2026-08-01
>    - Rust 0.10.0 was released on 2026-07-20
>    - C++ 0.3.0 was released on 2026-06-14
>
> Specs:
>
>    - Iceberg REST catalog spec added read restrictions to support
>    fine-grained
>    access control use cases, and labels to exchange catalog-owned
>    metadata.
>    - Expressions: Added the expression spec for storing and exchanging
>    expressions,
>    Updated REST protocol to include extended expressions.
>    - Indexes: A draft spec for scalar indexes is in review
>    - Tables: A draft spec for CHECK constraints is in review
>    - Tables: The changes for v4 adaptive metadata is in review
>
> PyIceberg 0.12.0:
>
>    - Support for Python 3.14
>    - Commit retry support
>    - New file format API
>    - View support
>    - Geometry and Geography type support
>
> Rust 0.10.x:
>
>    - Schema evolution: addition and removal of columns are now supported
>    - Added ExpireSnapshotsAction to expire old snapshots according to
>    table policy
>    - Tokio runtime is now configurable
>    - Parquet content-defined chunking table properties are now respected
>    - Catalogs now support purge operations; some existing operations
>    renamed from
>    drop to purge
>    - REST Catalog can now be queried for optional supported endpoints
>
> C++ 0.3.0:
>
>    - Added commit retries and merging snapshot updates
>    - Implemented reachability-based garbage collection
>    - Updated FileIO to support streams and bulk deletes
>    - Implemented merge-on-read
>    - Added nanosecond timestamp support
>    - Added a Puffin reader and writer
>    - Implemented OAuth2 token refresh for REST
>    - Added metrics reporting for scan and commit
>    - Added SQL catalog implementation
>
> Terraform 0.1.0:
>
>    - Initial release of the Terraform provider!
>
> Community Health:
>
> The community continues to be healthy and make swift progress. To keep up
> with
> the pace, this and future reports, project activity for implementations
> will be
> based on released changes, not what has been committed.
>
> The community is preparing the next Iceberg Summit, scheduled for April
> 2027.
>
> Contributors have reported that GMail has begun to classify Iceberg dev@
> emails
> as spam in many cases. There appears to be no solution other than to add a
> rule
> to prevent this. Other communities appear to be affected by the issue as
> well.
>

Reply via email to