MegaBites-AI/Windows-powershell

1# Issue Management2 3## Security Vulnerabilities4 5If you believe that there is a security vulnerability in PowerShell,6first follow the [vulnerability issue reporting policy](../../.github/SECURITY.md) before submitting an issue.7 8## Long-living issue labels9 10Issue labels for PowerShell/PowerShell can be found [here](https://github.com/powershell/powershell/labels).11 12### Issue and PR Labels13 14Issues are opened for many different reasons.15We use the following labels for issue classifications:16 17* `Issue-Announcement`: the issue is for discussing an [Announcement](https://github.com/PowerShell/Announcements)18* `Issue-Bug`: the issue is reporting a bug19* `Issue-Code Cleanup`: the issue is for cleaning up the code with no impact on functionality20* `Issue-Discussion`: the issue may not have a clear classification yet.21  The issue may generate an [RFC][ln-rfc] or may be reclassified as a bug or enhancement.22* `Issue-Enhancement`: the issue is more of a feature request than a bug.23* `Issue-Meta`: an issue used to track multiple issues.24* `Issue-Question`: ideally support can be provided via other mechanisms,25  but sometimes folks do open an issue to get a question answered and we will use this label for such issues.26 27[ln-rfc]: https://github.com/PowerShell/PowerShell-RFC28 29When an issue is resolved, the following labels are used to describe the resolution:30 31* `Resolution-Answered`: the issue was an `Issue-Question` and was answered.32* `Resolution-By Design`: the issue is not considered a bug, the behavior is working as designed.33* `Resolution-Duplicate`: the issue is a duplicate - there must be a comment linking to another issue.34* `Resolution-External`: the issue cannot be address by this repo.  Should be addressed externally.35* `Resolution-Fixed`: the issue has been fixed and should be referenced from a PR.36* `Resolution-Won't Fix`: the issue may be considered a bug or enhancement but won't be fixed.37  If there is an inadequate explanation as to why the issue was closed,38  anyone should feel free to reopen the issue.39 40### Feature areas41 42These labels describe what feature area of PowerShell that an issue affects.43Those labels denoted by `WG-*` are owned by a Working Group (WG) defined44[here](../community/working-group-definitions.md):45 46* `Area-Maintainers-Build`: build issues47* `Area-Cmdlets-Core`: cmdlets in the Microsoft.PowerShell.Core module48* `Area-Cmdlets-Utility`: cmdlets in the Microsoft.PowerShell.Utility module49* `Area-Cmdlets-Management`: cmdlets in the Microsoft.PowerShell.Management module50* `Area-Documentation`: PowerShell *repo* documentation issues, general PowerShell doc issues go [here](https://github.com/PowerShell/PowerShell-Docs/issues)51* `Area-DSC`: DSC related issues52* `Area-PowerShellGet`: PowerShellGet related issues53* `Area-SideBySide`: side by side support54* `WG-DevEx-Portability`: anything related to authoring cross-platform or cross-architecture55  modules, cmdlets, and scripts56* `WG-DevEx-SDK`: anything related to hosting PowerShell as a runtime, PowerShell's APIs,57   PowerShell Standard, or the development of modules and cmdlets58* `WG-Engine`: core PowerShell engine, interpreter, and runtime59* `WG-Engine-Performance`: core PowerShell engine, interpreter, and runtime performance60* `WG-Engine-Providers`: built-in PowerShell providers such as FileSystem, Certificates,61   Registry, etc. (or anything returned by `Get-PSProvider`)62* `WG-Interactive-Console`: the console experience63* `WG-Interactive-Debugging`: debugging PowerShell script64* `WG-Interactive-HelpSystem`: anything related to the help infrastructure and formatting of help65* `WG-Interactive-IntelliSense`: tab completion66* `WG-Interactive-PSReadline`: PSReadline related issues67* `WG-Language`: parser, language semantics68* `WG-Quality-Test`: issues in a test or in test infrastructure69* `WG-Remoting`: PSRP issues with any transport layer70* `WG-Security`: security related areas such as [JEA](https://github.com/powershell/JEA)71 72### Operating Systems73 74These are for issues that are specific to certain Operating Systems:75 76* `OS-Linux`77* `OS-macOS`78* `OS-Windows`79* `OS-WSL`: Windows Subsystem for Linux80 81### Process Tags82 83The following labels are used on PRs:84 85* `Review - Needed` : The PR is being reviewed.  Please see [Pull Request - Code Review](https://github.com/PowerShell/PowerShell/blob/master/.github/CONTRIBUTING.md#pull-request---code-review)86* `Review - Waiting on Author` : The PR was reviewed by the team and requires changes or comments from the author before being accepted.87* `Review - Abandoned` : The PR was not updated for a significant number of days (the exact number could vary over time).88  Maintainers should look into such PRs and re-evaluate them.89* `Review - Committee` : The PR/Issue needs a review from [powershell-committee](../community/governance.md#powershell-committee)90 91### Miscellaneous labels92 93* `Blocked` : An issue cannot be addressed due to external factors,94  but should not be closed because those external factors are temporary.95* `BVT/DRT` : An issue affecting or exposed by tests that have not been open sourced.96* `Changelog Needed` : The PR requires an addition to the changelog,97  and should be removed when it has been added.98* `Committee-Reviewed` : The PR/Issue has been reviewed by the [powershell-committee](../community/governance.md#powershell-committee)99* `Compliance` : Issues with the compliance label are required to be fixed either in the long term or short term for100  Microsoft to continue to sign and release packages from the project as official Microsoft packages.101  The time frame in which it needs to be fixed should be identified in the issue.102* `Documentation Needed` : The PR has changes that require a documentation change or new documentation added to [PowerShell-Docs](https://github.com/powershell/powershell-docs)103* `First-Time-Issue` : An issue that is identified as being easy and a good candidate for first time contributors104* `Hackathon` or `Hacktoberfest` : An issue that would be a good candidate for hackathons such as `Hacktoberfest` or `Hackillinois`105* `Porting` : An issue that affects a feature not yet ported to other platforms.106* `Up-for-Grabs` : We've acknowledged the issue but have no immediate plans to address it.107  If you're looking for a way to contribute, these issues can be a good place to start.108* `Usability` : This label is used to help us filter issues that might be higher priority109  because they more directly affect the usability of a particular feature or area.110* `Waiting - DotNetCore` : An issue waiting on a fix/change in DotNetCore.111