Copilot commented on code in PR #360: URL: https://github.com/apache/ozone-site/pull/360#discussion_r2901198169
########## docs/08-developer-guide/04-project/02-release-guide.md: ########## @@ -567,6 +567,23 @@ This step requires the release's [Docker image](#publish-a-docker-image-for-the- 3. Create a row for the next release in the `Upcoming Releases` section, and add planned features that you are aware of. +### Update Apache Release Metadata + +1. Mark the version as released in Apache Jira HDDS project: https://issues.apache.org/jira/plugins/servlet/project-config/HDDS/administer-versions?status=unreleased +2. A PMC member should add the release in Apache project metadata: https://reporter.apache.org/addrelease.html?ozone + +### Deprecate or Remove Old Releases + +When a release is superseded or no longer supported, clean up old release references. + +1. Remove unneeded artifacts from the Apache distribution SVN: + + ```bash + svn rm -m "Ozone: delete old version <old_version>" https://dist.apache.org/repos/dist/release/ozone/<old_version> Review Comment: The placeholder `<old_version>` in the `svn rm` command will be interpreted by most shells as input redirection because of the `<` character, so copy/pasting this snippet can fail or behave unexpectedly. Use a safe placeholder format (e.g., `OLD_VERSION`, `${OLD_VERSION}`, or a concrete example version like `1.2.0`) in both the commit message and URL. ```suggestion svn rm -m "Ozone: delete old version ${OLD_VERSION}" https://dist.apache.org/repos/dist/release/ozone/${OLD_VERSION} ``` -- 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]
