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
Which was last updated in March 2023 (one year ago).
But the same value for ROCm 6.1RC is 3614 ATM.
Please keep this public repo in sync with the ROCm that is released and with the ROCm RC.
This version number is useful to track which changes are where. I don't understand how the version here in the public repo was not updated for a year? while there are ongoing commits to this public repo. Is this a problem with the version number being out-of-sync, or is the situation that changes to CLR since one year ago didn't make it here in the open yet?
The text was updated successfully, but these errors were encountered:
@preda : We update the version when we merge changes from our development branch (amd-staging) to mainline branch (amd-mainline). The commit you are looking at is in the development branch in which we do not bump this version. Please refer to https://github.com/ROCm/clr/blob/amd-mainline/rocclr/utils/versions.hpp#L31 where you can see that the version is being regularly updated.
In rocclr/utils/versions.hpp there is:
clr/rocclr/utils/versions.hpp
Line 31 in ad32e60
Which was last updated in March 2023 (one year ago).
But the same value for ROCm 6.1RC is 3614 ATM.
Please keep this public repo in sync with the ROCm that is released and with the ROCm RC.
This version number is useful to track which changes are where. I don't understand how the version here in the public repo was not updated for a year? while there are ongoing commits to this public repo. Is this a problem with the version number being out-of-sync, or is the situation that changes to CLR since one year ago didn't make it here in the open yet?
The text was updated successfully, but these errors were encountered: