kevinjqliu commented on issue #872: URL: https://github.com/apache/iceberg-python/issues/872#issuecomment-2231426786
Seems like we have a way forward for nightly build. We can run the Pypi upload on a GitHub action nightly cron. I want to take a step back and talk about the general release process. I want to figure out how to shorten the burden of the release process so that we can release at a faster cadence. The [release instructions](https://py.iceberg.apache.org/how-to-release/) document several steps of the process - set git tag - sign files with GPG and upload to SVN - upload to Pypi - email devlist about new release Are these steps all necessary to release a new version? Is there room for automation similar to the Pypi automation above? Can we use the Github Release process somehow? -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
