Skip to content

Release Iceberg Rust (0.11.0) #3034

Closed
Closed

Description

@mbutrovich

Is your feature request related to a problem or challenge?

Tracking ticket for next release, also a place to track desired inclusions.

Features to mention in the blog (if they make it)

  • TBD

Bugs that should be fixed

  • TBD

Community Wishlist

  • TBD

Activity

  1. dannycjones commented on Aug 20, 2026

    @dannycjones
    Contributor

    I've drafted changes to the release guide that I'd like to see exercised for the next release! #3037

  2. dannycjones commented on Aug 25, 2026

    @dannycjones
    Contributor

    I'm happy to volunteer as release manager for 0.11.0. I also have an offer from @CTTY to support the steps that require committer privilege.

    It would be great to verify that the release runs smoother with the improvements made from #2864, and release changes that have been merged since we cut 0.10.x in June. I'm not aware of any blockers right now. I'd like to understand if anyone has anything they feel should block the 0.11.x branch being cut - please comment if so!

  3. CTTY commented on Aug 25, 2026

    @CTTY
    Collaborator

    Thanks Danny! I'm leaning toward having a fast release without adding extra blockers.

    DataFusion 55 has been released and we haven't released a Iceberg rust version with the stable DataFusion 54.1.

  4. dannycjones commented on Aug 27, 2026

    @dannycjones
    Contributor
  5. Kurtiscwright commented on Aug 31, 2026

    @Kurtiscwright
    Contributor

    Should we move off nightly as part of this release now that the version has been upgraded? While thinking about this Rust is currently on version 1.98, should we increase the MSRV beyond 1.95

  6. dannycjones commented on Sep 1, 2026

    @dannycjones
    Contributor

    Should we move off nightly as part of this release now that the version has been upgraded? While thinking about this Rust is currently on version 1.98, should we increase the MSRV beyond 1.95

    Kurtis and I had a quick chat about this. I'm not sure what the motivation is for testing on nightly and personally I'd prefer we simplify by sticking to stable too. Kurtis will follow-up with a new dev@ list e-mail to gauge opinions, but I think this can be left in 0.12 scope.

  7. dannycjones commented on Sep 2, 2026

    @dannycjones
    Contributor

    Agreement on the mailing list is to start 0.11 release process: https://lists.apache.org/thread/qs3tmtsg122l4pfsc7vx6pg4ngtx961x

    Just waiting on the must have changes here before we move forward: #3034 (comment)

    After that, I'll ask Shawn or another committer to cut the release branch and open the crate version bump and changelog PR against that as the base branch.

  8. CTTY commented on Sep 3, 2026

    @CTTY
    Collaborator

    I just created a new branch 0.11.x: https://github.com/apache/iceberg-rust/tree/0.11.x

  9. kevinjqliu commented on Sep 10, 2026

    @kevinjqliu
    Contributor

    Found a blocking issue and replied on the vote thread.

    Heres the proposed fix: #3184
    If we end up cutting a new RC i think we should include #3174 as well

    EDIT: Claude also suggest to include the pyo3 0.29 bump from main, which closes the two advisories currently ignored in the audit config.

  10. kevinjqliu commented on Sep 10, 2026

    @kevinjqliu
    Contributor

    I also opened #3185 to change how we handle new crates. Our current "publish the new crate by hand after the workflow fails" instructions don't work anymore now that we publish with cargo publish --workspace. More details in the PR.

    The short version: reserve the crate name on crates.io when the crate is added, not at release time. And add a PR CI check to enforce it.

    For 0.11.0, someone with crates.io access needs to reserve iceberg-property-macro before RC2. After that the release publishes through the workflow like normal.

  11. pinned and unpinned a comment on Sep 10, 2026
  12. dannycjones commented on Sep 10, 2026

    @dannycjones
    Contributor

    Thanks @kevinjqliu, particularly for the process improvements - these are great.

    I think next steps are:

  13. mbutrovich commented on Sep 10, 2026

    @mbutrovich
    CollaboratorAuthor

    One of these two PRs might be good to get into 0.11 since @CTTY specifically requested them as followups to get into the 0.11 release: #3180 #3145. #3145 has a review round, but no author response, #3180 I think has all of the feedback incorporated.

  14. 21 remaining items

  15. dannycjones commented on Oct 20, 2026

    @dannycjones
    Contributor

    We should get this one merged into 0.11.x branch too, it explains that 0.11.x are the last releases run by the Apache Iceberg project and points users where to find info on the new crate versions (which may or may not be the same crate, TBD).

    #3491

  16. dannycjones commented on Oct 20, 2026

    @dannycjones
    Contributor

    Adding a comment here to fold into the release guide when updated: Cutting a new branch to replace the old one is fine. We don't have to skip the old release.

    For 0.11.x, we're electing to continue with this release as is since this will be the last release of the Apache DataFusion integration governed by the Apache Iceberg project, which has since moved here: https://github.com/apache/datafusion-iceberg/.

  17. kevinjqliu commented on Oct 20, 2026

    @kevinjqliu
    Contributor

    Im trying to unblock the release by fixing the pyiceberg-core LICENSE/NOTICE issue.

    I see @dannycjones has already raised #3380 and #3414. Thank you!
    I also did some research and experiment and came up with a solution that I think is simpler and more easy to maintain. Here are the related PRs, please take a look!

  18. dannycjones commented on Oct 26, 2026

    @dannycjones
    Contributor

    Remaining steps for 0.11.0 RC3:

  19. dannycjones commented on Oct 27, 2026

    @dannycjones
    Contributor

    Some notes for retrospective:

    • We should add branch protection to main for the release branches as we cut them. That way, PRs behave the same way as on main with respect to merge queuing, required checks, etc..
  20. dannycjones commented on Oct 27, 2026

    @dannycjones
    Contributor

    Current next steps:

  21. dannycjones commented on Oct 27, 2026

    @dannycjones
    Contributor

    Kudos @kevinjqliu for getting the last few PRs reviewed and merged ❤️

    Next step: cut RC3 following the release guide https://rust.iceberg.apache.org/release#create-release-candidate-tag-and-artifacts

  22. CTTY commented on Oct 28, 2026

    @CTTY
    Collaborator

    I will cut the RC3 and will update the issue here!

  23. dannycjones commented on Nov 3, 2026

    @dannycjones
    Contributor

    The 0.11.0 RC3 vote passed! https://lists.apache.org/thread.html/rfc6bc7lq1xllv2hd4sy80qy39d1vlcc

    Next step is to promote this release candidate as an official release available on crates.io (along with other ASF distribution artifacts).

    Guide on next steps: https://rust.iceberg.apache.org/release#official-release

  24. dannycjones commented on Nov 3, 2026

    @dannycjones
    Contributor

    I think RC promotion can only be done by PMC, so there's an action item here to make that clear in the release guide.

  25. dannycjones commented on Nov 4, 2026

    @dannycjones
    Contributor

    Following https://rust.iceberg.apache.org/release.html#promote-the-rc

    export iceberg_version=0.11.0
    export rc=3
    dev/release/release.sh ${iceberg_version} ${rc}
    git push origin "v${iceberg_version}"
    

    Created the v1.11.0 tag, https://github.com/apache/iceberg-rust/releases/tag/v0.11.0

    Both publish and publish-python workflows are running

    * https://github.com/apache/iceberg-rust/actions/runs/41736189335 ✅
    
    * https://github.com/apache/iceberg-rust/actions/runs/41736203006 ✅
    

    Crates:

    * https://crates.io/crates/iceberg/0.11.0
    
    * https://crates.io/crates/iceberg-catalog-loader/0.11.0
    
    * https://crates.io/crates/iceberg-catalog-rest/0.11.0
    
    * https://crates.io/crates/iceberg-catalog-hms/0.11.0
    
    * https://crates.io/crates/iceberg-catalog-s3tables/0.11.0
    
    * https://crates.io/crates/iceberg-catalog-glue/0.11.0
    
    * https://crates.io/crates/iceberg-catalog-sql/0.11.0
    
    * https://crates.io/crates/iceberg-storage-opendal/0.11.0
    
    * https://crates.io/crates/iceberg-cache-moka/0.11.0
    
    * https://crates.io/crates/iceberg-property-macro/0.11.0
    
    * https://crates.io/crates/iceberg-datafusion/0.11.0
    

    Pypi:

    * https://pypi.org/project/pyiceberg-core/
    

    Github Release: https://github.com/apache/iceberg-rust/releases/tag/v0.11.0

    Last 2 items:

    * Send the announcement
    
    * Publish the release blog post
    

    @dannycjones @CTTY would you like to take this?

    Yes I'll take care of these, thanks Kevin!

  26. mbutrovich commented on Nov 4, 2026

    @mbutrovich
    CollaboratorAuthor

    I opened the 0.12.0 release ticket #3628

    So we can close this whenever everything is closed out on the 0.11.0 release. Thanks everyone!

  27. tafia commented on Nov 6, 2026

    @tafia

    Thanks a lot!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions