NVIDIA-NeMo / NVIDIA-NeMo/Curator

[Docs epic] Close post-v1.2.0 documentation gaps for 26.07

Open
#2,118 8 comments 0 reactions 1 assignee View on GitHub

@lbliii is already working on this.

Since Jun 29, 2026.

documentation roadmap
Dominant language
Python
Stars
1.8k
Forks
328
Avg merge
4d 5h
Merged PRs (30d)
30

Description

Goal

Close every actionable documentation gap introduced after NeMo Curator v1.2.0, and make the next release's docs/release notes complete enough for users to adopt new features and migrate breaking behavior.

Audit boundary and method

  • Primary boundary: commits reachable from main but absent from the v1.2.0 tag, reviewed through PR #2116 (merged 2026-06-29 19:34:32 UTC)
  • Original inventory: 67 PRs merged after the v1.2.0 publication timestamp
  • Supplemental code-freeze audit: 22 additional release-relevant PRs identified by Sara that merged after the 26.04 code freeze but before the release publication timestamp
  • Evidence reviewed: PR titles/bodies, changed file paths, git v1.2.0..main, and the current fern/versions/main/pages/ documentation tree
  • Decision rule: create focused docs work for user-facing features, public API/configuration changes, behavior changes, and migration hazards; bundle smaller release-note and reference gaps instead of creating noise

The publication timestamp alone was insufficient: it omitted release-relevant commits that missed v1.2.0 despite merging before the release was published. The supplemental disposition is tracked in NVIDIA-NeMo/Curator#2144, NVIDIA-NeMo/Curator#2145, and NVIDIA-NeMo/Curator#2146.

Planned documentation workstreams

  • NVIDIA-NeMo/Curator#2120 — Publish 26.07 release notes and a migration checklist
  • NVIDIA-NeMo/Curator#2119 — Document the Nemotron-CLIMB curation recipe
  • NVIDIA-NeMo/Curator#2123 — Document audio tagging, quality metrics, normalization, and LLM PnC
  • NVIDIA-NeMo/Curator#2122 — Document long-form audio cutting for ALM pretraining
  • NVIDIA-NeMo/Curator#2121 — Document the Nemotron OCR synthetic-data pipeline
  • NVIDIA-NeMo/Curator#2125 — Document the video caption-quality evaluation workflow
  • NVIDIA-NeMo/Curator#2124 — Replace legacy resumability guidance and document deterministic task identity
  • NVIDIA-NeMo/Curator#2126 — Complete the experimental translation configuration reference
  • NVIDIA-NeMo/Curator#2127 — Document filetype-aware deduplication input defaults
  • NVIDIA-NeMo/Curator#2128 — Document new Nemotron-Parse tuning and metrics
  • NVIDIA-NeMo/Curator#2129 — Document stage scheduling/configuration overrides across Ray Data and Xenna
  • NVIDIA-NeMo/Curator#2146 — Rewrite InferenceServer docs for typed Ray Serve and Dynamo backends
  • NVIDIA-NeMo/Curator#2145 — Update the video caption model matrix and Qwen migration
  • NVIDIA-NeMo/Curator#2144 — Close late code-freeze docs and release-note gaps
  • NVIDIA-NeMo/Curator#2168 — Document arm64/aarch64 platform constraints for audio curation

Child issues are linked above for traceability.

Complete PR disposition

Dedicated docs workstreams required (18)

These PRs add or change user-facing workflows/APIs and need more than a release-note bullet:

#1727, #1835, #1863, #1898, #1899, #1980, #2033, #2036, #2038, NVIDIA-NeMo/Curator#2045, NVIDIA-NeMo/Curator#2054, #2058, #2062, #2070, #2072, #2077, NVIDIA-NeMo/Curator#2086, NVIDIA-NeMo/Curator#2110

Release-notes or migration coverage required (8)

These are smaller fixes, platform constraints, or already-partially-documented removals. They belong in the release/migration task rather than separate feature pages:

#2024, #2049, #2053, #2055, #2057, #2104, NVIDIA-NeMo/Curator#2107, NVIDIA-NeMo/Curator#2109

Documentation already landed; verify in release sweep (9)

No standalone follow-up is currently justified, but the release-notes owner should verify navigation, versioning, and consistency:

#1983, #1961, #1991, #2000, #2029, #2030, #2071, NVIDIA-NeMo/Curator#2096, #2114

No public docs change required (32)

Dependency/security lockfile updates, CI/release plumbing, test-only changes, and internal benchmark-harness maintenance:

#1966, #2001, #2002, #2009, #2021, #2022, #2026, #2032, #2035, #2039, #2041, #2043, #2046, #2047, #2048, #2068, #2079, #2081, #2082, #2083, #2084, #2085, #2087, #2088, NVIDIA-NeMo/Curator#2091, #2099, #2100, #2103, #2105, NVIDIA-NeMo/Curator#2108, NVIDIA-NeMo/Curator#2115, #2116

Supplemental code-freeze disposition

Sara's follow-up list added 22 release-relevant PRs that were outside the original publication-time query.

New dedicated or bundled workstreams
Added to existing workstreams
  • Nemotron-CLIMB (NVIDIA-NeMo/Curator#2119): #1427
  • Audio tagging (NVIDIA-NeMo/Curator#2123): #1679
  • Translation (NVIDIA-NeMo/Curator#2126): #1844
  • Python migration/release notes (NVIDIA-NeMo/Curator#2120): #1855
Bundled release-note coverage (NVIDIA-NeMo/Curator#2144 and NVIDIA-NeMo/Curator#2120)

#1746, #1762, #1763, #1774, #1870, #1880, #1888, #1890

Epic-level acceptance criteria

  • Every PR in the dedicated and release-only buckets is covered by a child issue or an explicit release-note entry
  • fern/versions/main/pages/about/release-notes/index.mdx describes 26.07 rather than 26.04
  • Breaking changes and removed/renamed options have migration instructions
  • New pages are included in Fern navigation and pass docs validation
  • Code samples match the merged APIs and avoid user-supplied task_id
  • Links between concept, tutorial, API-reference, and release-note pages are complete
  • Each child issue records the PRs it closes documentation coverage for

Out of scope

  • Re-documenting internal benchmark infrastructure
  • Adding public docs for dependency-only or CI-only changes
  • Backporting new 26.07 feature docs into frozen v26.04 pages unless a correction is required

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.