Skip to content

Conversation

@Mr-Tao
Copy link

@Mr-Tao Mr-Tao commented Mar 20, 2023

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.

@ghost ghost added area-Infrastructure-libraries community-contribution Indicates that the PR has been added by a community member labels Mar 20, 2023
@ghost
Copy link

ghost commented Mar 20, 2023

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.

Issue Details

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.

Author: Mr-Tao
Assignees: -
Labels:

area-Infrastructure-libraries, community-contribution

Milestone: -

@ViktorHofer
Copy link
Member

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.

@Mr-Tao Mr-Tao changed the title Add missing OL releases to RID graph [releaso/6.0] Add missing OL releases to RID graph Mar 20, 2023
@Mr-Tao Mr-Tao changed the title [releaso/6.0] Add missing OL releases to RID graph [release/6.0] Add missing OL releases to RID graph Mar 20, 2023
@Mr-Tao
Copy link
Author

Mr-Tao commented Mar 20, 2023

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?

@carlossanlop
Copy link
Contributor

carlossanlop commented Mar 24, 2023

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.

@ghost ghost locked as resolved and limited conversation to collaborators Apr 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-Infrastructure-libraries community-contribution Indicates that the PR has been added by a community member

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants