In .NET 6.0, the dotnet/source-build repo is no longer the center of the source-build universe. This is because source-build is now initiated from the dotnet/installer repo. What is particularly confusing is the dotnet/source-build main branch is still part of source-build but in a minor roll. As time goes on, it would not be surprising to see source-build issues being opened in the dotnet/installer repo. The following is a list of suggestions on how to provide clarity and better UX going forward.
- Move the contents of the main branch into a new repo named more appropriately for it's purpose (e.g. source-build-externals). Add a single readme in dotnet/source-build that directs readers to the appropriate location - dotnet/installer for >= 6.0 and dotnet/source-build release branched for <= 5.0.
Move source-build issue tracking to dotnet/installer.
- Enable GH discussions in dotnet/source-build
- Add issue template to dotnet/installer to redirect source-build issues to dotnet/source-build
- Add curated content to dotnet/source-build to foster the maintainer network
In .NET 6.0, the dotnet/source-build repo is no longer the center of the source-build universe. This is because source-build is now initiated from the dotnet/installer repo. What is particularly confusing is the dotnet/source-build main branch is still part of source-build but in a minor roll. As time goes on, it would not be surprising to see source-build issues being opened in the dotnet/installer repo. The following is a list of suggestions on how to provide clarity and better UX going forward.
Move source-build issue tracking to dotnet/installer.