Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
As we announced earlier, we're planning on consolidating some of the repositories in the dotnet org. While this is still work in progress, we'd like to give you an update on where we are.
So far, we've identified the following repos:
You might notice that we changed our mind on naming from our earlier announcement. Based on your feedback, we decided to go with dotnet/runtime instead of dotnet/platform and dotnet/sdk instead of dotnet/cli.
Several people pointed out that the previous names weren't relatable to how we talk about the product, for example on download pages. So, we decided to match the product distributions as the primary design point for the new names. We generally refer to the bits you need to run your app as the runtime and the bits you need to build apps as the SDK. This also matches the naming chosen by other platforms.
New repos can't be used for .NET Core 3.x or earlier
The consolidated repositories are going to be about .NET 5 and going forward. It will not be possible to build .NET Core 3.1 or earlier from these repositories. As such, only the master branch from each of the repositories will be brought forward. There will be no porting of the individual release branches in the source repositories.
Personal names and email addresses
Since we're planning on rebasing the history in the merged repositories, we can map your name and email address to new values as well. We primarily do this to support our friends in the LGBTQ+ community who have changed their names to reflect their identities. However, anybody is welcome to use this to change their email and name.
Whatever your reason might be: we value your contributions and we hope this small gesture makes your life a little bit better. So if you changed your name/email – or simply prefer us to use different values – please submit a request.
More is coming
We'll share more updates in the upcoming months. Please let us know of any concerns that we haven't addressed yet!
To discuss these plans, please comment on the corresponding issue at dotnet/coreclr#27096.