(Initial proposal) |
m (Setting back to ChangePageIncomplete because, as discussed in email, this was submitted way too late for F32) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 34: | Line 34: | ||
* Name: [[User:omajid| Omair Majid]] | * Name: [[User:omajid| Omair Majid]] | ||
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | <!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. --> | ||
* Email: omajid@redhat.com | * Email: omajid@redhat.com | ||
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo) | ||
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | * FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address> | ||
| Line 189: | Line 189: | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> Please note: .NET Core 3.1 packages are already built. So there's no contingency plan needed now. | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Latest revision as of 15:02, 16 March 2020
.NET Core 3.1
Summary
Add .NET Core 3.1 packages, including the .NET Core SDK and Runtime, to Fedora
Owner
- Name: Omair Majid
- Email: omajid@redhat.com
Current status
- Targeted release: Fedora 32
- Last updated: 2020-03-16
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
.NET Core is an open source cross-platfrom runtime for developers to write and run applications. It particularly focuses on creating console applications and micro-services. It is the successor to the closed/proprietary/non-portable .NET Framework. The Fedora .NET SIG has been working with upstream .NET Core folks to try and make .NET Core completely buildable from source (instead of prebuilt binaries). With a recent release of .NET Core 3.1, we have achieved this. As "First" is one of Fedora's missions, we think Fedora should be the first distribution to include .NET Core built completely from source.
.NET Core 3.1 is an Long-Term Support release, supported by upstream until Dec 2022.
We have built .NET Core 3.1 in Fedora rawhide/33 as well as Fedora 32.
Benefit to Fedora
This provides a new language stack to Fedora: .NET.
This makes Fedora a more attractive platform for developers looking to migrate from .NET on Windows to the cross-platform .NET Core.
Previously, we were suggesting users to use a copr repository maintained by Fedora .NET SIG members. This makes that process smoother.
Scope
- Proposal owners:
The .NET Core maintainers (and the .NET SIG) will build and test the .NET Core packages in Fedora.
- Other developers: N/A (not a System Wide Change)
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- Policies and guidelines: N/A (not a System Wide Change)
No changes to any packaging guidelines are needed yet. We will investigate and propose changes for applications using .NET Core packages when we have some examples of packages using the .NET Core stack.
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
The following new packages should be available and installable:
dotnet-sdk-3.1dotnet-runtime-3.1aspnetcore-runtime-3.1dotnet
N/A (not a System Wide Change)
User Experience
.NET is one of the most popular programming platforms in the world. Developers using Fedora can now build and run .NET Core applications on Fedora.
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) Please note: .NET Core 3.1 packages are already built. So there's no contingency plan needed now.
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
N/A (not a System Wide Change)
Release Notes
.NET Core 3.1 is now available in Fedora 32.