Document how NVIDIA releases differ from CCCL releases - #10614
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe branching strategy documents NVIDIA-owned, read-only ChangesBranching strategy
Suggested reviewers: Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/maintainers/branching_strategy.rst (1)
23-24: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick winsuggestion: Clarify that
ctk/X.Y.xstarts from the exact contents of the corresponding CUDA Toolkit release and may then include additive internally developed features. The current wording can imply that the branch remains an unchanged release snapshot.Source: Path instructions
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: c29d30b7-4d23-4411-9222-83592481f759
📒 Files selected for processing (1)
docs/maintainers/branching_strategy.rst
|
|
||
| - Branches from ``branch/X.Y.x`` meant for representing exact contents of CUDA Toolkit Releases | ||
| - Created by NVIDIA. May contain internally developed features that are additive with the release it was based on. | ||
| - This is a read-only branch. |
There was a problem hiding this comment.
Should also answer when is this branch created? And how?
Co-authored-by: Jake Hemstad <jhemstad@nvidia.com>
⏱️ CCCL compile-time benchmark comparison: Public headers compile-time benchResult: 0 regression row(s), 26 improvement row(s) above threshold.
Artifacts: reports and traces TU total compilation
🟢 TU total compilation — Improvements
Direct file processing
🟢 Direct file processing — Improvements
|
Description
closes
Checklist