HonahX commented on issue #2419: URL: https://github.com/apache/polaris/issues/2419#issuecomment-3300546911
@MonkeyCanCode Thanks for for all the working on this topic. I see another place of enhancement and would like to learn your thoughts! Currently the wheel we build is specific to our local OS, e.g. ``` polaris-1.0.0-cp313-cp313-macosx_15_0_arm64.whl ``` I think it will be more convenient to include wheels for other OS and archs to users. We could leverage `cibuildwheel` to achieve this. For example, in pyiceberg, we have a Github Action workflow configured for release candidate build: https://github.com/apache/iceberg-python/blob/6e018c85af73bbc0250620e8d046bc08f9dfb121/.github/workflows/pypi-build-artifacts.yml#L64-L77 It will ends up build wheels for all os-arch-python combinations we want, like https://dist.apache.org/repos/dist/release/iceberg/pyiceberg-0.10.0/ The release process would be: - The release manager trigger the configured Github workflow - Download the generated artifacts (wheels) - release manager sign/compute checksum and publish it to svn with other files in the release candidate For reference: https://py.iceberg.apache.org/how-to-release/#create-artifacts If we think the above process makes sense, I could construct a workflow for this. -- 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]
