Skip to content

[release/6.0] Add missing Oracle RIDs - #66684

Closed
Mr-Tao wants to merge 2 commits into
dotnet:release/6.0from
Mr-Tao:oracle/6.0/add-missing-rids
Closed

[release/6.0] Add missing Oracle RIDs#66684
Mr-Tao wants to merge 2 commits into
dotnet:release/6.0from
Mr-Tao:oracle/6.0/add-missing-rids

Conversation

@Mr-Tao

Copy link
Copy Markdown

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

@ghostghost added community-contribution Indicates that the PR has been added by a community member area-Infrastructure-libraries and removed community-contribution Indicates that the PR has been added by a community member labels Mar 15, 2022
@dnfadmin

dnfadmin commented Mar 15, 2022

Copy link
Copy Markdown

CLA assistant check
All CLA requirements met.

@ghost

Copy link
Copy Markdown

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
Copy Markdown
Member

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

@Mr-Tao

Copy link
Copy Markdown
Author

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
Copy Markdown
Member

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

@wfurt

Copy link
Copy Markdown
Member

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

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

Copy link
Copy Markdown
Contributor

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

@ghostghost locked as resolved and limited conversation to collaborators Oct 19, 2022
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

area-Infrastructure-librariesNO-MERGEThe 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.

7 participants

@Mr-Tao@dnfadmin@agocke@akoeplinger@wfurt@carlossanlop@ViktorHofer