jbonofre commented on code in PR #4650: URL: https://github.com/apache/polaris/pull/4650#discussion_r3386646510
########## site/content/community/release-guides/semi-automated-release-guide.md: ########## @@ -164,17 +164,61 @@ We will proceed with publishing the approved artifacts and sending out the annou ## Publish the release The final workflow to run is [`Release - 4 - Publish Release After Vote Success`](https://github.com/apache/polaris/actions/workflows/release-4-publish-release.yml). This workflow will: * Verify that the release branch HEAD matches the last RC tag -* Copy artifacts from the dist dev to the dist release SVN repository -* Update the Helm index in dist release repository accordingly * Create a final release tag * Rebuild and publish Docker images to Docker Hub -* Create a Github release with the release artifacts +* Create a Github release with the release artifacts (downloaded from dist dev) * Release the candidate repository on Apache Nexus This workflow can only be run from the `release/[major].[minor].x` branch for which a vote has passed. The workflow verifies that no commits have been added to the release branch since the last RC was created. It also requires the Nexus staging repository id (`orgapachepolaris-<ID>`) that was created by the previous workflow.  +### Manual steps on dist.apache.org + +The workflow does not move artifacts from the dist dev to the dist release SVN repository, because the credentials used by the workflow do not have write access to the release area. A PMC member (or release manager with Apache SVN credentials) must run the following commands manually after the workflow completes. Review Comment: Let me clean this up. -- 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]
