Skip to content

ASP.NET Core area label consolidation #29725

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
JunTaoLuo opened this issue Jan 28, 2021 · 1 comment
Closed

ASP.NET Core area label consolidation #29725

JunTaoLuo opened this issue Jan 28, 2021 · 1 comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Milestone

Comments

@JunTaoLuo
Copy link
Contributor

Goals

Last week, we discussed the idea of consolidating some of the labels we use for issue management. The main goals of this effort are:

  1. Reduce the number of mis-tagged issues due to the confusion of which area labels should be applied
  2. Make the labels more clearly indicate which group/triage is responsible for tracking the filed issues

Update to area labels

Considering the above goals, we are proposing to conslidate some existing labels into area-servers and update the scope of area-infrastructure.

Specifically:

area-servers

This is a new area and will be owned by the Servers aka K-Core team. It will include all the functionality covered by the current tags:

area-azure
area-caching
area-hosting
area-httpclientfactory
area-middleware
area-servers
area-websockets
part of area-platform

Issues that fall under these areas will continue to be triaged during the K-Core triage and replacement feature-* tags will be used for clarification and organization purposes. The features tags are optional and are not mandatory until triaged by the K-Core team. The features also ensure we don't lose granularity in organizing aspnetcore issues. Currently, some issues in area-platform are tagged as such since it affects aspnetcore as a whole. These issues will be tagged with area-servers without any specific feature tag. For example, #27270

area-infrastructure

This existing area will be owned by the Build v-team and be updated to include all the functionality covered by the current tags:

area-infrastructure
area-installers
part of area-platform

Issues that fall under these areas will be triaged during the Build standup. A replacement feature-installers will replace the area-installers tag. The issues in area-plaform that are categorized as mechanically more related to infrastructure will be moved into this area. For example, #25917

unaffected areas

The following areas will not change in content:

area-dataprotection
area-grpc
area-healthchecks
area-identity
area-signalr
area-blazor
area-commandlinetools
area-mvc
area-perf
area-razor.compiler
area-razor.tooling
area-security
@JunTaoLuo JunTaoLuo added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Jan 28, 2021
@JunTaoLuo JunTaoLuo added this to the Discussions milestone Jan 28, 2021
@ghost
Copy link

ghost commented Mar 29, 2021

Thank you for contacting us. Due to a lack of activity on this discussion issue we're closing it in an effort to keep our backlog clean. If you believe there is a concern related to the ASP.NET Core framework, which hasn't been addressed yet, please file a new issue.

This issue will be locked after 30 more days of inactivity. If you still wish to discuss this subject after then, please create a new issue!

@ghost ghost closed this as completed Mar 29, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Apr 28, 2021
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

No branches or pull requests

1 participant