maxmustermann/dotnet-core
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Merge pull request #390 from terrajobst/roadmap

Browse source 
Update .NET Core Roadmap
This commit is contained in:
Immo Landwerth 2016-12-12 17:09:45 -08:00 committed by GitHub
commit f3fce7d408
1 changed files with 132 additions and 79 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

211
roadmap.md
View file

@ -1,110 +1,163 @@
.NET Core Roadmap
=================
# .NET Core Roadmap
.NET Core is a general purpose, modular, cross-platform and open source implementation of .NET. It includes a runtime, framework libraries, compilers and tools that support a variety of chip and OS targets. These components can be used together or separately.
Our primary focus is to get the .NET Core 1.0 tooling to RTM quality for the
Visual Studio 2017 RTM ([please try the 2017 RC update][vs2017-rc] we shipped
today with improvements in this area).
However, we are also starting to think of the next version of the runtime.
Because of this, if you follow our repositories you will start to see .NET Core
2.0 versioning. While we are still in the process of planning the next release,
there are some big themes you will identify in the early work on GitHub:
[vs2017-rc]: https://blogs.msdn.microsoft.com/dotnet/2016/12/12/updating-visual-studio-2017-rc-net-core-tooling-improvements/
* **.NET Standard 2.0**. Having a large set of common APIs that are consistent
across .NET Framework, .NET Core and Xamarin making it easier to share code
across those platforms and making it easier for package authors to build NuGet
packages. .NET Core gain over 5,000 APIs from .NET Framework as part of this
work. You can follow this work in the
[dotnet/standard](https://github.com/dotnet/standard) repo.
* **.NET Core Tooling**. Evolve the tooling aligned with the next .NET Core
runtime release. This will include tooling for choosing which .NET Core
version to target, to change the version of .NET Core for existing projects,
full package IntelliSense in .csproj files and more. You can follow this work
in the
[dotnet/roslyn-project-system](https://github.com/dotnet/roslyn-project-system),
[dotnet/sdk](https://github.com/dotnet/sdk), and
[microsoft/msbuild](https://github.com/microsoft/msbuild) repos.
* **Performance**. Continue to make the performance of building .NET Core
applications faster, especially in the inner loop. This is the cycle of
changing the source code and then restarting the application and making that
as fast as possible. You can follow this work
[dotnet/corefxlab](https://github.com/dotnet/corefxlab/blob/master/docs/roadmap.md)
repo.
* **.NET Core and Cloud**. Continue to improve how you run .NET Core
applications in Azure. Better logging, tracing and diagnosing errors in your
applications when running in the cloud. You can follow this work in the
[dotnet/corefx](https://github.com/dotnet/corefx) and
[aspnet](https://github.com/aspnet) repos.
* **Build from Source**. Make it very easy to clone the .NET Core repository and
GitHub and build the product. Great for experimenting with customizing the
product or trying to get it to run on Linux distributions other than the ones
we officially support. You can follow the bulk of the work in the
[dotnet/coreclr](https://github.com/dotnet/coreclr) and
[dotnet/corefx](https://github.com/dotnet/corefx) repos.
As mentioned above these are just some of the early themes we are going to
invest in. After we ship VS 2017 RTM you will hear more from us on the next
version of .NET Core, and as always let us know what is important to you.
## Ship Dates
| Milestone | Release Date |
|-------------------|--------------|
| .NET Core 2.0 | Spring 2017 |
| .NET Standard 2.0 | Spring 2017 |
# Components
.NET Core is a general purpose, modular, cross-platform and open source
implementation of .NET. It includes a runtime, framework libraries, compilers
and tools that support a variety of chip and OS targets. These components can be
used together or separately.
Major .NET Core components:
- [Runtime](https://github.com/dotnet/coreclr)
- [Libraries](https://github.com/dotnet/corefx)
- [C#/VB compiler](https://github.com/dotnet/roslyn)
- [CLI tools](https://github.com/dotnet/cli)
- [NuGet](https://github.com/NuGet/Home)
- [MSBuild](https://github.com/microsoft/msbuild)
* [Runtime](https://github.com/dotnet/coreclr)
* [Libraries](https://github.com/dotnet/corefx)
* [C#/VB compiler](https://github.com/dotnet/roslyn)
* [CLI tools](https://github.com/dotnet/cli)
* [NuGet](https://github.com/NuGet/Home)
* [MSBuild](https://github.com/microsoft/msbuild)
This roadmap is intended to communicate project priorities for evolving and extending the scope of .NET Core.
This roadmap is intended to communicate project priorities for evolving and
extending the scope of .NET Core.
Ship Dates
----------
At Microsoft, .NET has always been an important component of other teams' products and has largely shipped on their schedules. It means that we have to take their dates seriously and integrate them into the .NET Core schedule.
|Milestone|Release Date|
|---------|------------|
|1.2 | Spring 2017|
Planned 1.2 features
--------------------
- .NET Standard 2.0 support, bringing .NET Core to parity with .NET Framework and Mono for a large collection of base types.
Notes:
- The 1.0 release is accompanied with a preview version of the Visual Studio and command-line tooling. The Visual Studio tooling for 1.0 through 1.2 based on MSBuild and csproj should be publicly available in Fall 2016 and reach RTM quality in Spring 2017.
- The [ASP.NET Core roadmap](https://github.com/aspnet/Home/wiki/Roadmap) articulates the ASP.NET projects' roadmap and dates.
Technology Roadmaps
===================
# Technology Roadmaps
Architecture:
- [.NET Platform Standard](https://github.com/dotnet/corefx/blob/master/Documentation/architecture/net-platform-standard.md)
- [.NET Standard](https://github.com/dotnet/standard)
- [.NET Core Tools/CLI](https://docs.microsoft.com/en-us/dotnet/articles/core/tools/index)
Version 1.0 OS Support:
OS|Version|Architectures|Configurations|Notes
------------------------------|-------------------------------|----------|----------|---------|
Windows Client | 7 SP1 - 10 | x64, x86 | |
Windows Server | 2008 R2 SP1 - 2016 | x64, x86 | Full, Server Core, Nano (2016 only) |
Red Hat Enterprise Linux | 7.2 | x64 | |
Fedora | 23 | x64 | |
Debian | 8.2 | x64 | |
Ubuntu | 14.04 LTS, 16.04 LTS | x64 | |
Linux Mint | 17 | x64 | |
openSUSE | 13.2 | x64 | |
Centos | 7.1 | x64 | |
Oracle Linux | 7.1 | x64 | |
Mac OS X | 10.11, 10.12 | x64 | | 10.12 added in 1.0.2
OS |Version |Architectures|Configurations|Notes
------------------------------|-------------------------------|-------------|--------------|-----
Windows Client | 7 SP1 - 10 | x64, x86 | |
Windows Server | 2008 R2 SP1 - 2016 | x64, x86 | Full, Server Core, Nano (2016 only) |
Red Hat Enterprise Linux | 7.2 | x64 | |
Fedora | 23 | x64 | |
Debian | 8.2 | x64 | |
Ubuntu | 14.04 LTS, 16.04 LTS | x64 | |
Linux Mint | 17 | x64 | |
openSUSE | 13.2 | x64 | |
Centos | 7.1 | x64 | |
Oracle Linux | 7.1 | x64 | |
Mac OS X | 10.11, 10.12 | x64 | | 10.12 added in 1.0.2
There will be packages available for the native package managers for each OS. (e.g. apt-get, rpm, pkg, msi) as well as zips.
There will be packages available for the native package managers for each OS.
(e.g. apt-get, rpm, pkg, msi) as well as zips.
Microsoft provides commercially reasonable support for ASP.NET Core 1.0, .NET Core 1.0 and Entity Framework Core 1.0 on the OS and Version detailed in the table above.
Microsoft provides support for ASP.NET Core 1.0, .NET Core 1.0 and Entity Framework Core 1.0 on Windows, Linux, and Mac OS X. For an explanation of available support options, please visit [Support for Business and Developers](https://support.microsoft.com/en-us/gp/contactus81?Audience=Commercial&SegNo=4).
Microsoft provides commercially reasonable support for ASP.NET Core 1.0, .NET
Core 1.0 and Entity Framework Core 1.0 on the OS and Version detailed in the
table above. Microsoft provides support for ASP.NET Core 1.0, .NET Core 1.0 and
Entity Framework Core 1.0 on Windows, Linux, and Mac OS X. For an explanation
of available support options, please visit [Support for Business and
Developers](https://support.microsoft.com/en-us/gp/contactus81?Audience=Commercial&SegNo=4).
Project Goals
=============
# Project Goals
Broad goals:
- .NET Core code is high quality, has compelling performance, and is highly reliable.
- .NET Core can be ported to a broad set of OS platforms and chip architectures.
- .NET Core can be deployed with the application, side-by-side with other versions.
- .NET Core has a broad API surface that makes it suitable for most payloads.
- Developers can acquire a .NET Core developer environment quickly and intuitively.
- Developers can productively and intuitively build apps, using documentation, samples, community resources, and NuGet packages.
* .NET Core code is high quality, has compelling performance, and is highly
reliable.
* .NET Core can be ported to a broad set of OS platforms and chip architectures.
* .NET Core can be deployed with the application, side-by-side with other
versions.
* .NET Core has a broad API surface that makes it suitable for most payloads.
* Developers can acquire a .NET Core developer environment quickly and
intuitively.
* Developers can productively and intuitively build apps, using documentation,
samples, community resources, and NuGet packages.
Contributions
=============
# Contributions
Contribution goals:
Contribution goals:
- Encourage an active community welcoming contributions from all.
* Encourage an active community welcoming contributions from all.
The .NET Core maintainers have taken a liberal approach to contributions since the outset of the .NET Core open source project and have taken changes outside of the published [priorities](https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/project-priorities.md).
The .NET Core maintainers have taken a liberal approach to contributions since
the outset of the .NET Core open source project and have taken changes outside
of the published
[priorities](https://github.com/dotnet/coreclr/blob/master/Documentation/project-docs/project-priorities.md).
Microsoft Distro
================
# Microsoft Distro
Microsoft ships multiple .NET Core distros. It is important that Microsoft can successfully ship .NET Core at quality and meet its desired dates.
Microsoft ships multiple .NET Core distros. It is important that Microsoft can
successfully ship .NET Core at quality and meet its desired dates.
Other Distros
================
.NET Core will ship as part of many Linux distros and we are actively working with key partners in the Linux community to make it natural for .NET Core to go everywhere people need it. We are constantly looking to expand our distro support and welcome contributions and collaborations in this direction.
# Other Distros
Goals
-----
.NET Core will ship as part of many Linux distros and we are actively working
with key partners in the Linux community to make it natural for .NET Core to go
everywhere people need it. We are constantly looking to expand our distro
support and welcome contributions and collaborations in this direction.
- There are high-quality ports for Linux, macOS and Windows.
- There are high-quality ports for X64, X86, ARM32, and ARM64.
- .NET ships stable releases multiple times a year.
- Contributions should be prioritized that align with these goals.
## Goals
Workloads
---------
* There are high-quality ports for Linux, macOS and Windows.
* There are high-quality ports for X64, X86, ARM32, and ARM64.
* .NET ships stable releases multiple times a year.
* Contributions should be prioritized that align with these goals.
## Workloads
The Microsoft distro currently supports the following workloads:
- Console Apps
- ASP.NET Core
- Windows 10 UWP
* Console Apps
* ASP.NET Core
* Windows 10 UWP