Skip to content
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
1 change: 1 addition & 0 deletions docs/maintainers/issue-management.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@
Issues are opened for many different reasons.
We use the following labels for issue classifications:

* `Issue-Announcement`: the issue is for discussing an [Announcement](https://github.com/PowerShell/Announcements)
Copy link
Collaborator

@iSazonov iSazonov Jan 27, 2018

Choose a reason for hiding this comment

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

I agree with the label name. But I guess we need to change the color to dark yellow to not be confused with the red Issue-problems.
We could pin the Announce repo in https://github.com/PowerShell/

Also I suggest add two link in main Readme.md in https://github.com/PowerShell/PowerShell#new-to-powershell

@SteveL-MSFT I have some thoughts and concerns about Issue and PR workflow - could I email you?

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm ok with special casing this label to be a different color than the other Issue types because of it's special nature. I'll have the committee review this.

@iSazonov feel free to email me

* `Issue-Bug`: the issue is reporting a bug
* `Issue-Code Cleanup`: the issue is for cleaning up the code with no impact on functionality
* `Issue-Discussion`: the issue may not have a clear classification yet.
Expand Down