From Fedora Project Wiki
(Initial/partial proposal)
 
(Complete rest of the page)
Line 23: Line 23:
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->


<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
[[Category:SelfContainedChange]]
<!-- [[Category:SystemWideChange]] -->


* Targeted release: [[Releases/33 | Fedora 33 ]]  
* Targeted release: [[Releases/33 | Fedora 33 ]]  
Line 60: Line 58:
== Benefit to Fedora ==
== Benefit to Fedora ==


<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
This change improves the coverage of Fedora packages on aarch64. .NET Core was previously only available on x86_64; it's now available on aarch64 as well. Users who are using Fedora on aarch64 can now use the normal distribution packages for .NET Core, instead of having to find, download an installing .NET Core some other way. As a result of this, Fedora becomes a more attractive target for developing and deploying applications on aarch64.
 
      Be sure to include the following areas if relevant:
      If this is a major capability update, what has changed?
          For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
      If this is a new functionality, what capabilities does it bring?
          For example: This change allows package upgrades to be performed automatically and rolled-back at will.
      Does this improve some specific package or set of packages?
          For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
      Does this improve specific Spins or Editions?
          For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
      Does this make the distribution more efficient?
          For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
      Is this an improvement to maintainer processes?
          For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
      Is this an improvement targeted as specific contributors?
          For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.  


    When a Change has multiple benefits, it's better to list them all.
== Scope ==
 
* Proposal owners:  
    Consider these Change pages from previous editions as inspiration:
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
    https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
    https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
    https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
    https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->


== Scope ==
- Will update .NET Core to bootstrap and build on aarch64 (along with x86_64). This shouldn't affect any other packages.
* Proposal owners:
- Will work with package owners of any .NET Core dependencies on aarch64 if those specific dependencies of .NET Core are broken, buggy or un-available on aarch64
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: N/A [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
Line 106: Line 80:


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)  
N/A (not a System Wide Change)  


== How To Test ==
There is no known impact on upgrades.
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.  
 
.NET Core was just not available Fedora for aarch64 in previous releases of Fedora. It will be available in Fedora starting Fedora 33.


Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
.NET Core is not a dependency of any other package, so users running Fedora on aarch64 and then upgrading from Fedora 32 to 33 will not automatically pull it in. They will have to install it manually.


A good "how to test" should answer these four questions:
== How To Test ==


0. What special hardware / data / etc. is needed (if any)?
0. Install Fedora 33 on aarch64
1. How do I prepare my system to test this change? What packages
1. Install .NET Core: <code>sudo dnf install dotnet-sdk-3.1</code>
need to be installed, config files edited, etc.?
2. Run .NET Core: <code>dotnet --info</code>
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
The above steps should install .NET Core and show the .NET Core SDK and Runtime version numbers. There should be no error messages or any other failures.
N/A (not a System Wide Change)


== User Experience ==
== User Experience ==
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?


This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
- Users using Fedora on aarch64 as a platform for .NET Core development will be able to use the Fedora-provided packages for .NET Core
 
Describe what Users will see or notice, for example:
  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
-->


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Line 150: Line 109:


<!-- 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: Proposal owner will revert packaging changes and switch back to how .NET Core was built in Fedora 32.  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- 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 -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? No  
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? No
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==
Line 169: Line 126:
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
-->
-->
.NET Core is now available on aarch64! You can install .NET Core on Fedora on aarch64 using the normal packaging tools: <code>sudo dnf install dotnet-sdk-3.1</code>

Revision as of 14:42, 14 July 2020

.NET Core on Aarch64

Summary

.NET Core will now be available on Fedora on aarch64, in addition to x86_64.

Owner

Current status

  • Targeted release: Fedora 33
  • Last updated: 2020-07-14
  • 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

Fedora currently includes .NET Core only on x86_64. We want to make .NET Core available on Aarch64 as well for our users.

.NET Core documentation calls the Linux/aarch64 platform "linux-arm64".

This platform has been supported by upstream .NET Core for a little while now (2 years or so). But upstream cross-compile it on x86_64. With recent upstream improvements, we can now build .NET Core for aarch64 on aarch64.

In the spirit of being First on Fedora, we want to make .NET Core available for aarch64 on Fedora.

Feedback

We don't have any feedback at this time from the community.

Upstream is enthusiastic and supportive of us enabling this in Fedora.

Benefit to Fedora

This change improves the coverage of Fedora packages on aarch64. .NET Core was previously only available on x86_64; it's now available on aarch64 as well. Users who are using Fedora on aarch64 can now use the normal distribution packages for .NET Core, instead of having to find, download an installing .NET Core some other way. As a result of this, Fedora becomes a more attractive target for developing and deploying applications on aarch64.

Scope

  • Proposal owners:

- Will update .NET Core to bootstrap and build on aarch64 (along with x86_64). This shouldn't affect any other packages. - Will work with package owners of any .NET Core dependencies on aarch64 if those specific dependencies of .NET Core are broken, buggy or un-available on aarch64

  • Other developers: N/A (not a System Wide Change)
  • Release engineering: N/A #Releng issue number (a check of an impact with Release Engineering is needed)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

N/A (not a System Wide Change)

There is no known impact on upgrades.

.NET Core was just not available Fedora for aarch64 in previous releases of Fedora. It will be available in Fedora starting Fedora 33.

.NET Core is not a dependency of any other package, so users running Fedora on aarch64 and then upgrading from Fedora 32 to 33 will not automatically pull it in. They will have to install it manually.

How To Test

0. Install Fedora 33 on aarch64 1. Install .NET Core: sudo dnf install dotnet-sdk-3.1 2. Run .NET Core: dotnet --info

The above steps should install .NET Core and show the .NET Core SDK and Runtime version numbers. There should be no error messages or any other failures.

User Experience

- Users using Fedora on aarch64 as a platform for .NET Core development will be able to use the Fedora-provided packages for .NET Core

Dependencies

N/A (not a System Wide Change)

Contingency Plan

  • Contingency mechanism: Proposal owner will revert packaging changes and switch back to how .NET Core was built in Fedora 32.
  • Contingency deadline: N/A (not a System Wide Change)
  • Blocks release? No
  • Blocks product? No

Documentation

N/A (not a System Wide Change)

Release Notes

.NET Core is now available on aarch64! You can install .NET Core on Fedora on aarch64 using the normal packaging tools: sudo dnf install dotnet-sdk-3.1

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/.NETOnAarch64&oldid=582304"