X Tutup
Skip to content

Issue management #2197

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.

Sign up for GitHub

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
vors merged 4 commits into from
Sep 7, 2016
+12 −12
Merged

Issue management #2197

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4809ea1
punctuation: issue management
jsoref Sep 6, 2016
1c920d5
grammar: issue management
jsoref Sep 6, 2016
79ba4c3
capitalization: issue management
jsoref Sep 6, 2016
10364bc
miscellaneous: issue management
jsoref Sep 6, 2016
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
24 changes: 12 additions & 12 deletions docs/maintainers/issue-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,28 +9,28 @@ We use the following labels for issue classifications:

* `Issue-Bug`: the issue is reporting a bug
* `Issue-Discussion`: the issue may not have a clear classification yet.
The issue may generate a [RFC][ln-rfc] or maybe be reclassified as a bug or enhancement.
The issue may generate an [RFC][ln-rfc] or maybe be reclassified as a bug or enhancement.
Copy link
Copy Markdown
Contributor Author

@jsoref jsoref Sep 6, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason for an instead of a in an RFC is that RFC is pronounced arr, eff, cee and thus an arr-eff-cee is correct even though the first letter of RFC appears to be a consonant.

Copy link
Copy Markdown
Collaborator

@vors vors Sep 7, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, good to know :)

* `Issue-Enhancement`: the issue is more of a feature request than a bug.
* `Issue-Meta`: an issue used to track multiple issues
* `Issue-Meta`: an issue used to track multiple issues.
* `Issue-Question`: ideally support can be provided via other mechanisms,
but sometimes folks to open an issue to get a question answered and we will use this label for such issues.

[ln-rfc]: https://github.com/PowerShell/PowerShell-RFC

When an issue is resolved, the following labels are used to describe the resolution:

* `Resolution-Answered`: the issue was a `Issue-Question` and was answered.
* `Resolution-By Design`: the issue is not considered a bug, the behavior is working as designed
* `Resolution-Duplicate`: the issue is a duplicate - there must be a comment linking to another issue
* `Resolution-Answered`: the issue was an `Issue-Question` and was answered.
* `Resolution-By Design`: the issue is not considered a bug, the behavior is working as designed.
* `Resolution-Duplicate`: the issue is a duplicate - there must be a comment linking to another issue.
* `Resolution-External`: the issue cannot be address by this repo. Should be addressed externally.
* `Resolution-Fixed`: the issue is has been fixed and should be referenced from a PR
* `Resolution-Fixed`: the issue has been fixed and should be referenced from a PR.
* `Resolution-Won't Fix`: the issue may be considered a bug or enhancement but won't be fixed.
If there is an inadequate explanation as to why the issue was closed,
anyone should feel free to reopen the issue.

### Feature areas

These labels describe what feature area of PowerShell that an issue affects.
These labels describe what feature area of PowerShell that an issue affects:

* `Area-Build`: build issues
* `Area-Cmdlets`: cmdlets in any module
Expand All @@ -52,9 +52,9 @@ These labels describe what feature area of PowerShell that an issue affects.
* `Area-SideBySide`: side by side support
* `Area-Test`:issues in a test or in test infrastructure

### Operating systems
### Operating Systems

These are for issues that are specific to certain operating systems:
These are for issues that are specific to certain Operating Systems:
* `OS-Linux`
* `OS-macOS`
* `OS-Windows`
Expand All @@ -66,7 +66,7 @@ Issues can be in one of the following states:
* `0 - Backlog` : We've acknowledged the issue but have no immediate plans to address it.
If you're looking for a way to contribute, these issues can be a good place to start.
* `1 - Planning` : The issue requires some design or discussion before coding can begin.
* `2 - Ready` : Any design or discussion is essentially done, coding has not yet begun though.
* `2 - Ready` : Any design or discussion is essentially done, coding has not yet begun.
* `3 - Working` : The assignee(s) are actively working on the issue.
* `4 - In Review` : The issue is being reviewed.
The assignee(s) are responsible for signing off before the PR will be merged.
Expand All @@ -75,10 +75,10 @@ The following labels are used on PRs:

* `Review - Needed` : The PR is being reviewed. Please see [Pull Request - Code Review](../../.github/CONTRIBUTING.md#pull-request-code-review)
* `Review - Waiting on Author` : The PR was reviewed by the team and requires changes or comments from the author before being accepted.
* `Review - Abandoned` : The PR was not updated for significant number of days (the exact number could vary in time).
* `Review - Abandoned` : The PR was not updated for significant number of days (the exact number could vary over time).
Maintainers should look into such PRs and re-evaluate them.

### Random labels
### Miscellaneous labels
Copy link
Copy Markdown
Contributor Author

@jsoref jsoref Sep 6, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, the items may feel random, but we use misc. to describe an assortment of such items.


* `Blocked`: an issue cannot be addressed due to external factors,
but should not be closed because those external factors are temporary.
Expand Down
X Tutup