Skip to content

Commit

Permalink
Capitalize the first letter issues-policy.md (dotnet#8004)
Browse files Browse the repository at this point in the history
  • Loading branch information
vydao authored and mairaw committed Oct 2, 2018
1 parent 874b918 commit 122f8da
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions issues-policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ The goals of the process are:
1. Ensure errors or omissions in our docs are not blocking customer success.
1. Be responsive to customer feedback and concerns.
1. Continually improve the customer experience.
1. Learn more about customer experiences through open dialog on challenges and solutions.
1. Learn more about customer experiences through open dialog on challenges and solutions.

The process uses two stages to ensure responsiveness while prioritizing work. The initial stage diagnoses and triages the issue. The second stage resolves the issue. When an issue is both easy and urgent, the two stages may be combined.

Expand Down Expand Up @@ -48,9 +48,9 @@ Evaluating the correct course of action is subjective. The team members use thei

For other issues, the team:

- assigns a priority
- assigns a milestone, usually "Backlog"
- assesses if an issue is a good "up for grabs" issue, or the [Projects for .NET Community Contributors](https://github.com/dotnet/docs/projects/35)
- Assigns a priority
- Assigns a milestone, usually "Backlog"
- Assesses if an issue is a good "up for grabs" issue, or the [Projects for .NET Community Contributors](https://github.com/dotnet/docs/projects/35)

Priority levels are based on the following guidelines but are subjective. The milestones are also subjective and are based on other priorities such as current product release schedules and upcoming launches.

Expand Down

0 comments on commit 122f8da

Please sign in to comment.