[Epic] Build infrastructure improvements

javiercn commented 3 years ago

This issue collects all the individual issues for improvements that we want to do moving forward to our infrastructure.

Repo dev and contributor experience

[x] VS Code and VS 4 Mac experience. https://github.com/dotnet/aspnetcore/issues/27260
[ ] Updating public API files outside of Visual Studio. https://github.com/dotnet/aspnetcore/issues/27605
[x] Remove top-level build scripts in favor of area-specific build scripts (#27631)
[ ] Reduce E2E test dependencies. https://github.com/dotnet/aspnetcore/issues/27610
[ ] Add git pre-commit hooks for applying formatting to source (#27632)
[ ] Dynamically acquire dependencies needed for each project #27633
[ ] Improve experience for working with individual projects in the monorepo #27634

Complete Helix migration

[ ] Run hosting functional tests on Helix. https://github.com/dotnet/aspnetcore/issues/8247
[x] Run Components end to end tests on Helix. https://github.com/dotnet/aspnetcore/issues/6857

Codebase quality improvements

[ ] Regularly update our JavaScript dependencies to the latest versions https://github.com/dotnet/aspnetcore/issues/29925
[ ] Enable more code analyzers for the product. https://github.com/dotnet/aspnetcore/issues/24055
- The person working on this will drive the effort, which consists of choosing an initial set of analyzers to enable.
[x] Change default server for samples from IIS Express to Kestrel (#27630)

Testing reliability reporting tool

[ ] ~Bring back what's broken in some shape or form. https://github.com/dotnet/aspnetcore/issues/27606~

Performance readiness

[x] Ensure our microbenchmarks can run. https://github.com/dotnet/aspnetcore/issues/27607

Infrastructure code duplication removal

[x] Unify test/publish for helix/local scenarios https://github.com/dotnet/aspnetcore/issues/27296

Engineering system

[ ] Consider adding a shipping package baseline test https://github.com/dotnet/aspnetcore/issues/28129

Misc

[x] Switch to MIT license https://github.com/dotnet/aspnetcore/issues/18873

dougbu commented 3 years ago

Including this in the DoI project for discussion in that context

ghost commented 3 years ago

Thanks for contacting us. We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

mkArtakMSFT commented 3 years ago

Assigned this to 6.0 as we will plan to tackle individual items on this list throughout the preview releases.

ghost commented 1 year ago

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

dotnet / aspnetcore