snazy commented on code in PR #3476: URL: https://github.com/apache/polaris/pull/3476#discussion_r2708911452
########## site/content/community/release-guides/manual-release-guide.md: ########## @@ -465,11 +465,52 @@ You can now publish Docker images on DockerHub: ./gradlew :polaris-admin:assemble :polaris-admin:quarkusAppPartsBuild --rerun -Dquarkus.container-image.build=true -Dquarkus.container-image.push=true -Dquarkus.docker.buildx.platform="linux/amd64,linux/arm64" -Dquarkus.container-image.tag=x.y.z ``` -### Publishing docs -1. Open a PR against branch [`versioned-docs`](https://github.com/apache/polaris/tree/versioned-docs) to publish the documentation -2. Open a PR against the `main` branch to update website - - Add download links and release notes in [Download page](https://github.com/apache/polaris/blob/main/site/content/downloads/_index.md) - - Add the release in the [website menu](https://github.com/apache/polaris/blob/main/site/hugo.yaml) +### Upload the documentation +Now that the release artifacts have been published, the next step is to publish the associated documentation on the website. Checkout the `versioned-docs` branch locally and copy the documentation associated to the release tag at the root of the repository. + +``` +git checkout -b versioned-docs-[major].[minor].[patch] versioned-docs Review Comment: Nah, there's technically no issue w/ Git (it's smart ;) ). From experience, I'd recommend to remove the "inner worktree" as soon as possible, because IDEs like IntelliJ recognize the "inner worktree" and for example fold that history in the Git view, which is then a bit confusing. -- 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]
