You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is something we could do, if we backport the needed pieces from #165, and figure out a way to robustly keep both 11.8.x and 12.x docs updated (make the docs rebuildable as needed).
The only useful docs from 11.8.x are the API References and I can see the benefit of adding a versioned doc like 11.8.5 so that these become web accessible. Backporting only the needed pieces looks ok.
I'd hope to avoid requiring a new version each time a patch gets released but I'm not sure if that's ideal either since we had issue #140. If we decide that that issue is a one-off, then we could simplify the versioned doc to be 11.x and avoid extra work. Then when 13.0 arrives, we can create a version 12.x to follow suit. Again though because of that issue perhaps the extra work is justified. What do you think?
Activity
leofang commentedon Nov 13, 2024
@vzhurba01 WDYT?
vzhurba01 commentedon Nov 13, 2024
The only useful docs from 11.8.x are the API References and I can see the benefit of adding a versioned doc like
11.8.5so that these become web accessible. Backporting only the needed pieces looks ok.I'd hope to avoid requiring a new version each time a patch gets released but I'm not sure if that's ideal either since we had issue #140. If we decide that that issue is a one-off, then we could simplify the versioned doc to be
11.xand avoid extra work. Then when 13.0 arrives, we can create a version12.xto follow suit. Again though because of that issue perhaps the extra work is justified. What do you think?leofang commentedon Jan 13, 2025
#388 could be another motivation.
leofang commentedon Jun 4, 2025
We are dropping support for CUDA 11 very soon. This is moot.