Re: [Proposal] Automating the PyIceberg Release Process

Hey folks, Just following up on this thread. The `iceberg-python` release process has been updated at the "How to Release" documentation (#1391 ). The process now

Re: [Proposal] Automating the PyIceberg Release Process

Hey Kevin, I agree with your reasoning. Having reproducible builds would be nice, but it doesn't seem very popular in Pythonland. For example, cibuildwheel that we use, doesn't mention anything about reproducibility. The steps that your suggestion make sense

Re: [Proposal] Automating the PyIceberg Release Process

Hi Fokko, Thank you for pointing me to the ASF Release Policy, it was very informative! Based on the policies, we cannot automate signing in GitHub Actions because Python wheels are not considered reproducible [1]. The wheels include information about the current date and time, which prevents val

Re: [Proposal] Automating the PyIceberg Release Process

Hey Kevin, First of all, thanks for working on the releases, that's always much appreciated. Regarding the changes to the release process, I'm all for automating as much as possible, but I have some concerns. I also think it is important to split out nightly builds, and the release process in gen

[Proposal] Automating the PyIceberg Release Process

Hi everyone, As the release manager for PyIceberg 0.8.0 and the upcoming 0.8.1 release, I’ve taken some time to reflect on ways we could improve the release process. I drew inspiration from the iceberg-go release process and documented my notes here