Skip to content
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 Oracle RIDs #66684

Closed
wants to merge 2 commits into from

Conversation

Mr-Tao
Copy link

@Mr-Tao Mr-Tao commented Mar 15, 2022

This change adds previously missing RIDs for OL releases 7, 8 and 9 and respective RHEL counterparts.

@ghost ghost added the community-contribution Indicates that the PR has been added by a community member label Mar 15, 2022
@dotnet-issue-labeler dotnet-issue-labeler bot added area-Infrastructure-libraries and removed community-contribution Indicates that the PR has been added by a community member labels Mar 15, 2022
@dnfadmin
Copy link

dnfadmin commented Mar 15, 2022

CLA assistant check
All CLA requirements met.

@ghost
Copy link

ghost commented Mar 15, 2022

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

Issue Details

This change adds previously missing RIDs for OL releases 7, 8 and 9 and respective RHEL counterparts.

Author: Mr-Tao
Assignees: -
Labels:

area-Infrastructure-libraries

Milestone: -

@agocke
Copy link
Member

agocke commented Mar 15, 2022

This would need to go through main. Also, what's the justification for adding more RIDs?

@Mr-Tao
Copy link
Author

Mr-Tao commented Mar 16, 2022

This would need to go through main.

Sure can do. Did I miss any docs? How is this different from, e.g. #65392, #64304 or #66225?

Also, what's the justification for adding more RIDs?

There already are RIDs for OL 7 and 8 in the graph. This update is just adding current versions. Not to mention the addition of new RIDs is happening all the time: see #61304 or #62184, to list a few.

@akoeplinger
Copy link
Member

@carlossanlop do you know what the status of this one is?

@wfurt
Copy link
Member

wfurt commented Aug 22, 2022

we should resolve #66783 first IMHO @akoeplinger e.g. get it in main and than we can worry about back port.

@carlossanlop carlossanlop added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Sep 7, 2022
@carlossanlop
Copy link
Member

The main PR had to be closed due to inactivity. We can reopen this after the main one gets reopened and merged. #66783

@ghost ghost locked as resolved and limited conversation to collaborators Oct 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure-libraries NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants