This is an automated email from the ASF dual-hosted git repository. fokko pushed a commit to branch fd-update-release-process in repository https://gitbox.apache.org/repos/asf/iceberg.git
commit b66924e1aba9d78f21bee5869f10bd96afebbfda Author: Fokko Driesprong <[email protected]> AuthorDate: Mon Mar 11 15:46:04 2024 +0100 Use `svn mv` when releasing the binaries This will avoid having to clone everything locally. --- site/docs/how-to-release.md | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/site/docs/how-to-release.md b/site/docs/how-to-release.md index c775a718c4..bfc9ddb432 100644 --- a/site/docs/how-to-release.md +++ b/site/docs/how-to-release.md @@ -34,7 +34,7 @@ This page describes the procedures that the release manager and voting PMC membe To create a release candidate, you will need: -* Apache LDAP credentals for Nexus and SVN +* Apache LDAP credentials for Nexus and SVN * A [GPG key for signing](https://www.apache.org/dev/release-signing#generate), published in [KEYS](https://dist.apache.org/repos/dist/dev/iceberg/KEYS) If you have not published your GPG key yet, you must publish it before sending the vote email by doing: @@ -256,14 +256,7 @@ are prepared when going through the below steps. First, copy the source release directory to releases: ```bash -mkdir iceberg -cd iceberg -svn co https://dist.apache.org/repos/dist/dev/iceberg candidates -svn co https://dist.apache.org/repos/dist/release/iceberg releases -cp -r candidates/apache-iceberg-<VERSION>-rcN/ releases/apache-iceberg-<VERSION> -cd releases -svn add apache-iceberg-<VERSION> -svn ci -m 'Iceberg: Add release <VERSION>' +svn mv https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-<VERSION>-rcN https://dist.apache.org/repos/dist/release/iceberg/apache-iceberg-<VERSION> -m "Iceberg: Add release <VERSION>" ``` !!! Note
