Skip to content

[release/6.0] Add Fedora 37 RID - #65392

Merged
carlossanlop merged 2 commits into
dotnet:release/6.0from
omajid:rid-fedora-37
Jun 14, 2022
Merged

[release/6.0] Add Fedora 37 RID#65392
carlossanlop merged 2 commits into
dotnet:release/6.0from
omajid:rid-fedora-37

Conversation

@omajid

@omajidomajid commented Feb 15, 2022

Copy link
Copy Markdown
Member

Fedora 37 has now started development, and the distribution now
identifies itself as Fedora 37 instead of Fedora 36:
https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html

@ghost

ghost commented Feb 15, 2022

Copy link
Copy Markdown

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@ghostghost added the community-contribution Indicates that the PR has been added by a community member label Feb 15, 2022
@ericstj
ericstj requested a review from wfurtMarch 11, 2022 00:53
@ericstj

ericstj commented Mar 11, 2022

Copy link
Copy Markdown
Member

Should we make this change in main first before taking in release?

@wfurt

wfurt commented Mar 11, 2022

Copy link
Copy Markdown
Member

probably. But I think it would be OK to take it now here and do it in main tomorrow or next week. @carlossanlop noticed some differences how the RID is generated. We are probably ought to check all active branches to make sure the RIDs are the same. AFAIK that was our general goal, right?

@carlossanlopcarlossanlop added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Mar 11, 2022
@Mr-TaoMr-Tao mentioned this pull request Mar 16, 2022
Closed
omajid added a commit to omajid/dotnet-runtime that referenced this pull request Mar 23, 2022
@omajid
Add Fedora 37 RID
02d9379
Fedora 37 has now started development, and the distribution now
identifies itself as Fedora 37 instead of Fedora 36:
https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
This is a forward-port of dotnet#65392
@omajidomajid mentioned this pull request Mar 23, 2022
Merged
@ghost

ghost commented Mar 23, 2022

Copy link
Copy Markdown

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

Issue Details

Fedora 37 has now started development, and the distribution now
identifies itself as Fedora 37 instead of Fedora 36:
https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html

Author:omajid
Assignees:-
Labels:

NO-MERGE, area-Host, community-contribution

Milestone:-

wfurt
wfurt approved these changes Mar 23, 2022
View reviewed changes

@wfurtwfurt left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTMN.
But should we start with main/7.0 and roll it back to servicing?

@wfurt

wfurt commented Mar 23, 2022

Copy link
Copy Markdown
Member

LGTMN.
But should we start with main/7.0 and roll it back to servicing?

missed #67021

wfurt pushed a commit that referenced this pull request Mar 23, 2022
@omajid
Add Fedora 37 RID (#67021)
195c7e2
Fedora 37 has now started development, and the distribution now
identifies itself as Fedora 37 instead of Fedora 36:
https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
This is a forward-port of #65392
radekdoulik pushed a commit to radekdoulik/runtime that referenced this pull request Mar 30, 2022
@omajid@radekdoulik
Add Fedora 37 RID (dotnet#67021)
6de22ca
Fedora 37 has now started development, and the distribution now
identifies itself as Fedora 37 instead of Fedora 36:
https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
This is a forward-port of dotnet#65392
@rbhanda

rbhanda commented May 19, 2022

Copy link
Copy Markdown
Collaborator

dotnet/core#7467 to track support for Fedora 37

@omajid
Add Fedora 37 RID
a7e0032
Fedora 37 has now started development, and the distribution now
identifies itself as Fedora 37 instead of Fedora 36:
https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
@carlossanlopcarlossanlop removed the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Jun 14, 2022
@rbhanda

rbhanda commented Jun 14, 2022

Copy link
Copy Markdown
Collaborator

@wfurt looks like this has a merge conflict. Can we have this merge for the July servicing asap

@carlossanlop
carlossanlop merged commit 976694c into dotnet:release/6.0Jun 14, 2022
@rbhandarbhanda added Servicing-approved Approved for servicing release and removed Servicing-approved Approved for servicing release labels Jun 16, 2022
@rbhandarbhanda modified the milestones: 3.1.27, 6.0.7Jun 16, 2022
@ghostghost locked as resolved and limited conversation to collaborators Jul 16, 2022
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@wfurtwfurtwfurt approved these changes

Assignees

No one assigned

Labels

area-Hostcommunity-contributionIndicates that the PR has been added by a community memberServicing-approvedApproved for servicing release

Projects

None yet

Milestone

6.0.7

Development

Successfully merging this pull request may close these issues.

6 participants

@omajid@ericstj@wfurt@rbhanda@carlossanlop@danmoseley