September Issue/PR Grooming - review, categorization, assignment

[egamma]

During September we want to get our open issues down. As a first step we will review the assigned issues.

Review

During the review pass please make sure to:

• close obsolete/fixed issues
• each issue must have a type
  • Note: All type labels are grey (Bugs grey with a touch of red).
• assign the important label to issues that
  • result in data loss
  • a breakage of extension
  • critical security, performance issues
  • UI issue that makes a feature unusable
• each issue needs to be assigned to a feature area
• assign bugs that you plan to fix during September to the September milestone
• issues that the community can take up should be labeled as help-wanted
• if issues are suitable for beginners you can also add the good-first-issue label and add code pointers that help beginners to get started with a PR
• feature requests that should be implemented as extensions should be labeled extensions-candidate and be closed

Tracking:

Please make sure that you also do this grooming in our satellite repositories:

• @alexandrudima
• @weinand
• @chrmarti
• @Tyriar
• @dbaeumer
• @bpasero
• @egamma
• @isidorn
• @joaomoreno
• @jrieken
• @kieferrm
• @aeschli
• @rebornix
• @ramya-rao-a
• @roblourens
• @sandy081
• @mjbvz
• @octref
• @auchenberg
• @chrisdias
• @seanmcbreen (covered by @egamma)
• @danyeh

[bpasero]

@egamma there are issues assigned to people that are not showing up in the list to sign off:

• https://github.com/Microsoft/vscode/issues/assigned/auchenberg
• https://github.com/Microsoft/vscode/issues/assigned/chrisdias
• https://github.com/Microsoft/vscode/issues/assigned/seanmcbreen (!)
• https://github.com/Microsoft/vscode/issues/assigned/danyeh

[egamma]

@bpasero thanks updated the tracking section