Skip to content

Updates to Issue Guide #41

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

Merged
merged 2 commits into from
Dec 4, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions Documentation/issue-guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,11 +64,12 @@ If the issue is already assigned to someone, please coordinate with the assignee



## Upvotes on issues
## Prioritization & Upvoting

Upvotes on first post of each issue are useful hint for our prioritization.
* Upvotes on first post of each issue are a useful hint for our prioritization.
We can [sort issues by number of upvotes](https://github.com/dotnet/wpf/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) and we will review the top list on regular basis.

* We're most likely to include improvements that either have a positive impact on a broad scenario or have very significant positive impact on a niche scenario. We're less likely to prioritize modest improvements to niche scenarios.
* Compatibility will almost always be given a higher priority than improvements.


## Escalations
Expand All @@ -77,7 +78,6 @@ If you think some issue or PR is not getting the right attention, or if you noti
you can escalate to WPF team by tagging some of us (e.g. [@fabiant3](https://github.com/fabiant3), [@karelz](https://github.com/karelz)). Please do not overuse it.



## Triage rules

Guidance for triaging issues for WPF team members:
Expand Down