Skip to content

September Issue/PR Grooming - review, categorization, assignment #58336

@egamma

Description

@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:

Metadata

Metadata

Labels

plan-itemVS Code - planned item for upcoming

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions