Release Iceberg Rust (0.11.0)

[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

[dannycjones]

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

[dannycjones]

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!

[CTTY]

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.

[dannycjones]

Ahead of cutting the release branch...

Must haves:

• chore: Merge changes from 0.10.x to main #3074
• chore(ci): Fail CI when a publishable crate is missing LICENSE or NOTICE #3084

Should have:

• chore: Update MSRV to Rust 1.95 #3083

Nice to have:

• Changes proposed here: Release process retrospective 0.10.0 + 0.10.1 #2864

[Kurtiscwright]

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

[dannycjones]

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.

[dannycjones]

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.