docs: Add news items for FP8 Quantization, MoE optimization, and NeMo-RL V0.3

[snowmanwwg]

What does this PR do ?

Add a one line overview of what this PR aims to accomplish.

Issues

List issues that this PR closes (syntax):

Usage

• You can potentially add a usage example below

# Add a code snippet demonstrating how to use this

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you run the unit tests and functional tests locally? Visit our Testing Guide for how to run tests
• Did you add or update any necessary documentation? Visit our Document Development Guide for how to write, build and test the docs.

Additional Information

• ...

Summary by CodeRabbit

• Documentation
  • Updated the News section with new entries dated 9/27/2025 (FP8 Quantization in NeMo RL), 8/15/2025 (optimizing weight transfer in large MoE models), and 7/31/2025 (NeMo-RL V0.3: scalable, performant post-training).
  • Retained existing 9/25/2025 and 7/25/2025 items, keeping the 7/25/2025 entry as a parent with nested announcements.
  • No functional changes; informational updates only.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds three new News bullet items dated 9/27/2025, 8/15/2025, and 7/31/2025 to README.md, keeping existing 9/25/2025 and 7/25/2025 entries. No code or control flow changes.

Changes

Cohort / File(s)	Summary
Docs: README News updates README.md	Inserted three informational News entries (9/27/2025 FP8 Quantization in NeMo RL; 8/15/2025 NeMo-RL weight transfer in MoE; 7/31/2025 NeMo-RL V0.3), retained existing 9/25/2025 and 7/25/2025 items. No functional code changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• docs: Restructure README with backend-specific quick start and setup guides #1091 — Also changes README News/Previous News structure; likely intersects with how news items are organized.

Suggested labels

CI:docs

Suggested reviewers

• terrykong

Pre-merge checks and finishing touches

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Test Results For Major Changes	✅ Passed	This PR only updates the README with additional news entries, which is a documentation-only change and does not introduce new functionality, refactors, or any behavior-affecting modifications. Because the change is minor, the absence of explicit test results in the PR description is acceptable under the custom check criteria. Therefore the requirement concerning test documentation is satisfied by default.
Title Check	✅ Passed	The title accurately describes the primary change, namely adding news entries for FP8 Quantization, MoE optimization, and NeMo-RL V0.3 to the README documentation, and it follows a concise “docs:” prefix convention.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snowmanwwg-patch-2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1f979e0 and f881c3f.

📒 Files selected for processing (1)

• README.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

README.md

8-8: Unordered list indentation
Expected: 2; Actual: 4

(MD007, ul-indent)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: Docs_Tests
• GitHub Check: Lint check
• GitHub Check: Post submodule check comment / Comment on PR
• GitHub Check: Post automodel integration comment / Comment on PR

[terrykong]

@CodeRabbit title

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@terrykong, the current PR title "Update README.md" is quite generic. Based on the changes that add several news items to the README, here are some more descriptive title suggestions:

Recommended:

• docs: Add news items for FP8 Quantization, MoE optimization, and NeMo-RL V0.3
• docs: Update README with latest NeMo-RL announcements

Alternative options:

• Add September and August 2025 news updates to README
• Update README news section with recent NeMo-RL developments

The first suggestion follows conventional commit format and clearly describes what's being added to the documentation.

Would you like me to update the PR title for you?