chihsuan opened a new pull request, #457:
URL: https://github.com/apache/ozone-site/pull/457

   ## What changes were proposed in this pull request?
   
   Update the Release Manager Guide to reflect the new Docusaurus-based website 
workflow, since the website was migrated to render from the `master` branch of 
the ozone-site repo. The old Hugo/`asf-site` instructions no longer apply.
   
   Changes requested in the Jira:
   
   - Rewrite the "Update the Ozone Website" section: open a single PR against 
`master` in apache/ozone-site that updates the Downloads page 
(`src/pages/download.md`) and adds release notes under 
`src/pages/release-notes/`; test locally with `pnpm build` instead of `hugo 
serve`.
   - Drop the "Update the Ozone Roadmap" section, since the wiki is no longer 
used.
   - Fix the announcement mail links: release notes 
`https://ozone.apache.org/release/1.2.0/` -> 
`https://ozone.apache.org/release-notes/2.1.0`, download 
`https://ozone.apache.org/downloads/` -> `https://ozone.apache.org/download/`.
   
   Additional changes beyond the Jira description, to clean up stale content 
left behind by the same website migration and wiki deprecation:
   
   - "Write a Haiku": the national park tag was looked up on the now-deprecated 
Ozone Roadmap wiki page. Point to its actual source of truth instead: the 
`<ozone.release>` property in the project's top level pom (also shown by 
`bin/ozone version`).
   - "Update the Ozone Website": added a step to create a versioned copy of the 
documentation for the release (with apache/ozone-site#330 as an example). The 
removed "extract the docs folder from the release tarball" step was the docs 
publishing step, so dropping it without a replacement would leave the guide 
with no instruction for publishing the release's documentation.
   - "Patch Release": the website bullets still referenced the old site's 
`release/1.2.0` -> `release/1.2.1` redirect and a Hugo-era example PR 
(apache/ozone-site#23). Replaced them with the equivalent steps on the new 
site: replace the superseded release's row on the Downloads page, add release 
notes for the patch release, and remove the Downloads section from the 
superseded release's notes page (pointing readers to the patch release) since 
its artifacts are removed from the distribution site and redirects are not 
available in this setup.
   
   ## What is the link to the Apache Jira?
   
   https://issues.apache.org/jira/browse/HDDS-15427
   
   ## How was this patch tested?
   
   - `pnpm build` succeeds (also validates internal links/anchors).
   - `markdownlint` and `cspell` pass on the changed file.
   - Verified the rendered page locally with `pnpm start`.
   


-- 
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]

Reply via email to