Now that we've gotten enough of a sign-off from everyone involved in the governance process, the docs need to be reworked to use a consistent terminology set, links, and directory structure.
1.9 KiB
Issue Management
Long-living issue labels
Feature areas
These labels describe what feature area of PowerShell that an issue addresses.
Area-Build
: build issuesArea-Cmdlets
: cmdlets in any moduleArea-Console
: the console experienceArea-Debugging
: debugging PowerShell scriptArea-Documentation
: PowerShell repo documentation issues, general PowerShell doc issues go hereArea-Engine
: core PowerShell engine, interpreter, runtimeArea-Intellisense
: tab completionArea-Language
: parser, language semanticsArea-OMI
: omiArea-PackageManagement
: PackageManagement related issuesArea-Performance
: a performance issueArea-Portability
: anything affecting script portabilityArea-PSReadline
: PSReadLineArea-SideBySide
: Side by side supportArea-Test
: tests or test infrastructure
Operating systems
These are for issues that are specific to certain operating systems:
OS-Linux
OS-OS X
OS-Windows
Process Tags
Issues can be in one of the following states:
-
0 - Backlog
: We've acknowledged the issue but have no immediate plans to address it. -
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. -
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. -
help wanted
: We are looking for someone to work on this issue. -
need review
: This pull request is being reviewed. Please see Pull Request - Code Review -
waiting for author
: The issue or pull request needs -
add to changelog
: The PR requires an addition to the changelog. Should be removed when it has been added.