[new-product] Add nvidia-cuda.md #7452
Conversation
|
Thank you for opening this pull request 👍. If you are not familiar with the project, please check out our Contributing Guidelines and our Guiding Principles. Also take a look at our Hacking Guide if you intend to work on site internals. |
There was a problem hiding this comment.
each cycle has to have these fields : eol , latest , eoas ( because you have set eoasColumn as true)
also you couldnt add any future dated releases for example 2026-xx-xx
also all cycles should be ordered based on releaseDate otherwise it will fail in linting/building
|
Hi @adammw ! I'm interested in this as well. Here's some thoughts. NVIDIA does not seem to publish explicit EOL dates for their CUDA releases. However, they do have a EOL policy for their CUDA Toolkit images. This states that those images EOL along with the driver version it shipped, which has an explicit EOL policy defined in their releases.json file. I suggest we do the same here. I think the names nvidia-cuda and "CUDA libraries" is overly generic, as their are a number of CUDA libraries that do not live within the CUDA Toolkit. cudNN, python CUDA, etc. I suggest we rename this to explicitly just refer to the CUDA toolkit. Let me know how I can help! |
First attempt at documenting NVIDIA CUDA libraries