dannycjones commented on issue #2361: URL: https://github.com/apache/iceberg-rust/issues/2361#issuecomment-4799753694
I'm totally new to the Python bindings, but here's my current thoughts: - To fix the full release process, I'm considering the pull PyPI publishing out of the current reusable workflow for prod PyPI release, and put it in `publish.yml` (which gets us around the blocker on trusted publishing and reusable workflows). - There's a bit of duplication with the release and the nightly publishing of Python bindings. Given the move above already to make the workflow focus on package building only, we might consider having a reusable workflow for that alone and simply delegate. We might parameterize the workflow a bit, such that we say "this is nightly" or "this is an official release" and branch the matrix generation, etc. on that. Then `publish.yml` and `release_python_nightly.yml` can become thin wrappers on the bulk of the Python packaging workflows. I plan to focus on the first point for now - pulling PyPI publishing into `publish.yml` and unblocking releases - but I had tried to understand how we might better factor the workflows and figured I'd share my thinking if anyone is interested in picking that up. -- 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]
