-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/6.0] Add missing OL releases to RID graph #83681
Conversation
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries Issue DetailsI see that there is a decision to deprecate the RID graph (#83246) being contemplated. That effort seems to be the reason why this change didn’t get into the I think that getting rid of RIDs is a good idea. Before the plan comes to fruition we still need to keep supporting all the RIDs released so far. Therefore, I’m filing this change against the Merging the change should not impose any additional burden when the decision to drop RIDs gets approved. Meanwhile, it will relieve us of the great PITA of manually updating RIDs on every new erratum release.
|
Are these already in release/7.0 and main? It's unclear when the RID graph will be deprecated, hence porting them into all supported branches is recommended. |
I will happily do that, @ViktorHofer. Could you reopen (#81115) then, please? |
The PR in main had an ongoing discussion while closed. I think we should reopen the main PR, ping the people involved in making these decisions, continue the conversation there, and close this PR for now until we decide something. I hope that's ok with you, @Mr-Tao. We can't take servicing changes before main changes. |
I see that there is a decision to deprecate the RID graph (#83246) being contemplated. That effort seems to be the reason why this change didn’t get into the
main
branch (#81115).I think that getting rid of RIDs is a good idea. Before the plan comes to fruition we still need to keep supporting all the RIDs released so far. Therefore, I’m filing this change against the
release/6.0
branch, so that the support of Oracle Linux gets on par with other RHEL-derived distros, like Rocky or AlmaLinux.Merging the change should not impose any additional burden when the decision to drop RIDs gets approved. Meanwhile, it will relieve us of the great PITA of manually updating RIDs on every new erratum release.