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

Respond to feedback

Browse source
This commit is contained in:
Richard Lander 2015-09-10 22:26:18 -07:00
parent 1799a41138
commit 20c07c2c92
1 changed files with 33 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

57
roadmap.md
View file

@ -1,12 +1,14 @@
.NET Core Roadmap
=================
.NET Core is a general purpose, modular, cross-platform and open source implementation of .NET. The .NET Core team (anyone contributing to .NET Core) aspires to enable it to work for many interesting scenarios. Some of those are already part-way to completion. Nice work, team!
.NET Core is a general purpose, modular, cross-platform and open source implementation of .NET. It includes a set of [framework libraries](https://github.com/dotnet/corefx) and a [runtime](https://github.com/dotnet/coreclr). Both together support a set of OS platforms and chip architectures, enabling a broad set of .NET apps to be built and run. Much of this support is in progress.
The team (anyone contributing to .NET Core) is composed of many individuals and groups. They (separately) have been adding support for the scenarios they are most interested in. That ranges from Windows to FreeBSD. Some of the projects are half-way to completion. Nice work, team! Some contributors, likely companies, will create official distributions (AKA "distros") that they support and potentially sell as part of some offering. A distro is an official build of .NET Core (e.g. zip, apt-get, brew, msi), much like Linux distros.
Microsoft makes multiple "official" .NET Core distributions (libraries and/or runtime) available to its customers. It is expected (and desired) that other groups (corporations or otherwise) will also become significantly invested in .NET Core, making other distros available.
This roadmap is intended to communicate the team's priorities for evolving and extending the scope of .NET Core.
Microsoft is very invested in .NET Core and makes multiple "official Microsoft" .NET Core distributions available to its customers. Sweet! It is expected (and desired) that other groups (corporations or otherwise) will also become significantly invested in .NET Core, possibly making other distros available. As a result, this roadmap is written from a neutral perspective, not a Microsoft one (unless specifically called out). This document is therefore naturally open to PRs.
Project Goals
=============
@ -23,7 +25,19 @@ Active ports:
- OSes: Linux, OS X, FreeBSD, Rasberry Pi2 (Linux) and Windows.
- Linux distros: Debian family, CentOS.
- Windows versions: Win7+ (client and server).
- Chips: X64, X86, ARM32.
- Chips: X64, X86, ARM32, ARM64.
Contributions
=============
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). That approach isn't intended to change.
Contribution goals:
- Encourage an active community.
- Make changes easy to code review (smaller vs. bigger).
- Keep a single "repo of truth" for the project.
- Support multiple release trains (released, about to release, vNext).
Microsoft Distro
================
@ -38,25 +52,32 @@ Goals
- .NET Core can be shipped on a schedule that aligns with ASP.NET and Windows 10 UWP dates and quality (e.g. Beta, RTM) requirements.
- Contributions should be prioritized that align with these goals.
Workloads
---------
The Microsoft distro currently supports the following workloads.
- Console
- ASP.NET 5
- Windows 10 UWP
Ship Dates
----------
At Microsoft, .NET has always been an important component of other teams' products and has largely shipped on their schedules. It's important to have customers! It means that we have to take their dates seriously and integrate them into the .NET Core schedule.
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|Partner|Quality|
|---------|------------|-------|-------|
|Beta8 | Oct 2015|ASP.NET|Beta |
|RC1 | Nov 2015|ASP.NET|RC |
|v5 RTM | Q1 2016|ASP.NET|RTM |
|Milestone|Release Date|
|---------|------------|
|Beta8 | Oct 2015|
|RC1 | Nov 2015|
|RTM | Q1 2016|
Notes:
- The RC1 release candidate will be a supported and production ready cross-platform release.
- Depending on feedback from RC1, we will ship additional release candidates as necessary.
- The RTM release is **CY** Q1 2016.
- CoreFX API contracts may need to be at RTM quality in RC releases, to support the already RTM Windows 10 UWP release.
- The [ASP.NET 5 roadmap](https://github.com/aspnet/Home/wiki/Roadmap) articulates the ASP.NET projects's roadmap and dates.
- More partners will be added to this list over time.
Feature Roadmaps
================
@ -73,15 +94,3 @@ There are several areas of the product that are TBD. This designation doesn't me
- OS package manager support (e.g. apt-get, brew).
- Broader Linux distro support (beyond Debian and CentOS).
- Create low-level FX APIs for Linux (e.g. daemon support) and OSX, much like exists for Windows (e.g. Windows registry).
Contributions
=============
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). That approach isn't intended to change.
Contribution goals:
- Encourage an active community.
- Make changes easy to code review (smaller vs. bigger).
- Keep a single "repo of truth" for the project.
- Support multiple release trains (released, about to release, vNext).