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 Fedora 37 RID #65392

Merged
merged 2 commits into from
Jun 14, 2022
Merged

Conversation

omajid
Copy link
Member

@omajid omajid commented Feb 15, 2022

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

@dotnet-issue-labeler
Copy link

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.

@ghost ghost 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 wfurt March 11, 2022 00:53
@ericstj
Copy link
Member

ericstj commented Mar 11, 2022

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

@wfurt
Copy link
Member

wfurt commented Mar 11, 2022

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?

@carlossanlop carlossanlop added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Mar 11, 2022
omajid added a commit to omajid/dotnet-runtime that referenced this pull request Mar 23, 2022
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
@omajid omajid mentioned this pull request Mar 23, 2022
@ghost
Copy link

ghost commented Mar 23, 2022

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: -

Copy link
Member

@wfurt wfurt left a comment

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

wfurt commented Mar 23, 2022

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
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
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
Copy link
Contributor

rbhanda commented May 19, 2022

dotnet/core#7467 to track support for Fedora 37

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
@carlossanlop carlossanlop removed the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Jun 14, 2022
@rbhanda
Copy link
Contributor

rbhanda commented Jun 14, 2022

@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.0 Jun 14, 2022
@rbhanda rbhanda added Servicing-approved Approved for servicing release and removed Servicing-approved Approved for servicing release labels Jun 16, 2022
@rbhanda rbhanda modified the milestones: 3.1.27, 6.0.7 Jun 16, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jul 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Host community-contribution Indicates that the PR has been added by a community member Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants