dannycjones commented on issue #2907: URL: https://github.com/apache/iceberg-rust/issues/2907#issuecomment-5094515090
> > Blockers > > Are these really necessary? If possible, i'd like to release as is, with the same commit hash as 0.10.0. @kevinjqliu We at least need to update the Cargo manifests, which will require a new commit. CI against the 0.10 branch is currently failing, although personally I am OK with skipping. If we wanted to skip the crates release and do only pyiceberg-core, we'd need to modify the Python workflow to ignore Cargo and target version release mismatch. I don't have a lot of knowledge on the Python package release, so I'm hesitant to explore that unless there's more interest in avoiding the crates release. That being said, it looks fairly straightforward as its only validation then takes the value as given in the input to the workflow. I'm inclined (+0.5) to move forward with a simple patch release, pulling in minimal dependency updates such as the crossbeam issue. It's an effort on the community to validate again another round of release candidates, but I think this is the right process and may be a good forcing mechanism to ensure we have a reliable RC process. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
