From 79fccfdc61aa019d00084c97856f1d5cc98409e5 Mon Sep 17 00:00:00 2001 From: Sung Yun <107272191+syun64@users.noreply.github.com> Date: Tue, 30 Jul 2024 22:18:16 +0000 Subject: [PATCH] add more release notes --- mkdocs/docs/how-to-release.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/mkdocs/docs/how-to-release.md b/mkdocs/docs/how-to-release.md index 07e60895c4..20cd1e1a5c 100644 --- a/mkdocs/docs/how-to-release.md +++ b/mkdocs/docs/how-to-release.md @@ -208,6 +208,15 @@ svn add /tmp/iceberg-dist-release/ svn ci -m "PyIceberg " /tmp/iceberg-dist-release/ ``` + + +!!! note + Only a PMC member has the permission to upload an artifact to the release dist. + + + +### Upload the accepted release to PyPi + The latest version can be pushed to PyPi. Check out the Apache SVN and make sure to publish the right version with `twine`: ```bash @@ -243,3 +252,13 @@ Make sure to create a PR to update the [GitHub issues template](https://github.c ## Update the integration tests Ensure to update the `PYICEBERG_VERSION` in the [Dockerfile](https://github.com/apache/iceberg-python/blob/main/dev/Dockerfile). + +## Create a Github Release Note + +First, follow the directions for Setting the tag again to create a tag for the approved release version (e.g. `0.7.0`). + +Then, create a new [Release Note](https://github.com/apache/iceberg-python/releases) on the iceberg-python Github repository by clicking on **Draft a New Release**. + +Choose the approved release version as the tag and **Generate release notes**. + +**Set as the latest release** and **Publish**. \ No newline at end of file