gemmellr commented on code in PR #158: URL: https://github.com/apache/artemis-console/pull/158#discussion_r2713486583
########## Releasing.md: ########## @@ -179,20 +178,21 @@ Once the CDN and Maven Central are up-to-date then update the site as follows: 1. Run the release addition script to generate/perform most of the updates by running command of form: ``` -./scripts/release/add-artemis-console-release.sh <new-version> +./scripts/release/add-artemis-console-release.sh <path.to>/artemis-console <previous-version> <new-version> ``` This does the following: - Creates the new release collection file at `src/_artemis_console_releases/artemis-console-<padded-version-string>.md`. - Creates the new release notes file at `src/components/artemis-console/download/release-notes-<new-version>.md`. +- Creates a new directory for the documentation at `src/components/artemis-console/documentation/<new-version>` and copies the documentation into it from the build directory. +- Updates `.htaccess` file in `src/components/artemis-console/documentation` to properly reference the "latest" docs. Review Comment: I did think of an alternative that gives both a 'latest' dir and version-specific dirs the broker documentation can immediately reference...do the reverse of what this is currently doing. Use a stable 'latest' dir for the current docs, and redirect from \<latest-version-number\> --> latest. The 'add release script' then updates the redirect, and copies the old docs to the old version dir. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
