You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by "kevinjqliu (via GitHub)" <gi...@apache.org> on 2024/12/05 20:02:46 UTC
[I] Improve PyIceberg release process [iceberg-python]
kevinjqliu opened a new issue, #1306:
URL: https://github.com/apache/iceberg-python/issues/1306
### Feature Request / Improvement
Similar to #872
`iceberg-go` has a really nice release script https://github.com/apache/iceberg-go/blob/adc8193de3299b04c9763c2fba529a7b94d080ce/dev/release/release_rc.sh#L4
As the release manager for 0.8.0, I also took some notes on the release process and what we can improve
[PyIceberg 0.8.0 release notes](https://docs.google.com/document/d/1gPG8pZKavUgd-Avj4Od8qJSP7fCd9ga6x6qVqaaDw1w/edit?usp=sharing)
--
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-unsubscribe@iceberg.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] Improve PyIceberg release process [iceberg-python]
Posted by "Fokko (via GitHub)" <gi...@apache.org>.
Fokko closed issue #1306: Improve PyIceberg release process
URL: https://github.com/apache/iceberg-python/issues/1306
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] Improve PyIceberg release process [iceberg-python]
Posted by "kevinjqliu (via GitHub)" <gi...@apache.org>.
kevinjqliu commented on issue #1306:
URL: https://github.com/apache/iceberg-python/issues/1306#issuecomment-2521285301
reopening this to track further improvements
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] Improve PyIceberg release process [iceberg-python]
Posted by "kevinjqliu (via GitHub)" <gi...@apache.org>.
kevinjqliu commented on issue #1306:
URL: https://github.com/apache/iceberg-python/issues/1306#issuecomment-2521288955
#1391 captures improvements to build both PyPI and SVN artifacts in 1 GitHub action run and avoid problems like setting the wrong version/RC. The action is also now automatically run on relevant tag push.
The final release process should look something like this:
* prepare local branch for release (main for major/minor, branch for patch release)
* Create and push tag with RC (e.g. 0.8.1rc1)
* Tag push automatically triggers the GitHub Action
* Github action builds artifacts for both SVN and PyPI
* Download the SVN artifact, create checksum and signature, and upload to SVN dev dist
* Download Pypi artifact and upload it to PyPi
* Send vote email
* Once passed, download the artifact from SVN dev dist, upload it to SVN release dist, and PyPI
* If a new RC is needed, create and push another tag with RC (e.g. 0.8.1rc2)
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] Improve PyIceberg release process [iceberg-python]
Posted by "kevinjqliu (via GitHub)" <gi...@apache.org>.
kevinjqliu closed issue #1306: Improve PyIceberg release process
URL: https://github.com/apache/iceberg-python/issues/1306
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] Improve PyIceberg release process [iceberg-python]
Posted by "kevinjqliu (via GitHub)" <gi...@apache.org>.
kevinjqliu commented on issue #1306:
URL: https://github.com/apache/iceberg-python/issues/1306#issuecomment-2521534316
> The final release process should look something like this:
> * prepare local branch for release (main for major/minor, branch for patch release)
> * Create and push tag with RC (e.g. 0.8.1rc1)
> * Tag push automatically triggers the GitHub Action
> * Github action builds artifacts for both SVN and PyPI
> * Download the SVN artifact, create checksum and signature, and upload to SVN dev dist
> * Download Pypi artifact and upload it to PyPi
> * Send vote email
> * Once passed, download the artifact from SVN dev dist, upload it to SVN release dist, and PyPI
> * If a new RC is needed, create and push another tag with RC (e.g. 0.8.1rc2)
This can be further simplified with `make publish-rc`, which takes input `VERSION` and `RC`. Creates RC artifacts and publish to SVN and PyPi
* Create the tag based on the current branch.
* Checks `main` branch is used for major/minor, and the feature branch is used for patch i.e. `0.8.x`.
* Push tag to trigger GitHub action run
* Watch run
* Download artifacts
* Sign/Checksum/Upload to svn
* Upload to PyPI
After the vote passes, use `make promote-rc`, which takes input `VERSION` and `RC`. Download RC artifact from dev SVN, upload to release SVN and PyPi
* Download artifacts from SVN
* Upload to svn
* Upload to PyPi
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] Improve PyIceberg release process [iceberg-python]
Posted by "kevinjqliu (via GitHub)" <gi...@apache.org>.
kevinjqliu commented on issue #1306:
URL: https://github.com/apache/iceberg-python/issues/1306#issuecomment-2521292551
based on the devlist discussion https://lists.apache.org/thread/oowhcfwv3fcjzdzm76tbn99k5q84mr75
we'd also want to publish nightly build to PyPi (#872)
This can be done by reusing `pypi_build_artifacts` and `pypi_merge_artifacts` and uploading the final artifact to PyPi. Will work on this once #1391 is in
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org
Re: [I] Improve PyIceberg release process [iceberg-python]
Posted by "kevinjqliu (via GitHub)" <gi...@apache.org>.
kevinjqliu commented on issue #1306:
URL: https://github.com/apache/iceberg-python/issues/1306#issuecomment-2643450754
#1391 creates the `python-release.yml` which can be triggered by Github Actions and automatically build both SVN and PYPI artifacts. This PR also adds new release instructions
#1599 cleans up the `cibuildwheel` configs
#1600 splits out SVN build and PYPI build into separate components to be reuseable
#1601 reuses the PYPI build to automatically push a nightly version to testpypi
The release process is at a good state now! Release is more-or-less a one click process.
New release instructions are located at https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/how-to-release.md
--
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-unsubscribe@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org