Skip to content

Conversation

@jojochuang
Copy link
Contributor

What changes were proposed in this pull request?

HDDS-14313. [Website v2] Blog: Apache Ozone 2.0 release

Please describe your PR in detail:

  • Follow the standard Docusaurus convention to create blog posts under /blog directory.
  • Added the Apache Ozone 2.0 release announcement into the blog post using the github announcement.
Screenshot 2025-12-31 at 3 36 48 PM

What is the link to the Apache Jira?

https://issues.apache.org/jira/browse/HDDS-14313

How was this patch tested?

Check off which of the following tests were done on this change. If additional testing was done, please elaborate here as well.

  • The CI checks on my fork are passing
  • I verified the rendered content using a local preview
  • I manually verified the steps provided in this change work as described

Creates a new blog post for the Apache Ozone 2.0.0 release,
using the content from the GitHub release announcement.
- Enables the Docusaurus blog plugin.
- Creates a new blog post for the Apache Ozone 2.0.0 release.
- Migrates the blog content to the standard `blog` directory structure.
- Updates the navbar to point to the new blog.
@jojochuang jojochuang added the website-v2 Tasks for the new ozone website targeting the HDDS-9225-website-v2 branch label Dec 31, 2025

- ARM64 support (HDDS-6263).
- Java 11/17/21 Support and Testing (HDDS-8246).
- AWS SDK v2 client support (HDDS-11577).

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to the comments on HDDS-11577, AWS SDK v2 support was added in HDDS-12488

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for catching it. Updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

website-v2 Tasks for the new ozone website targeting the HDDS-9225-website-v2 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants