Skip to content

2019 Issue Grooming - review, categorization, assignment #82032

@kieferrm

Description

@kieferrm

During October we groom our open issues.

Preparation

Review Guidelines

In the first pass reviewing the issues has a higher priority than fixing issues. Clearly, we'll use common sense, i.e. we'll make easy fixes on the fly. During review please make sure:

  • to close obsolete/fixed issues and mark duplicates as appropriate,
  • that each issue has a type
  • that each issue is assigned to a feature area
  • that bugs that you plan to fix during October are assigned to the October milestone. Since the main focus is on housekeeping, be conservative.
  • to close out-of-scope feature requests assign the *out-of-scope label. Take into account that we'll have a "polishing, take care of smaller issues" milestone in early 2020. There is no value in keeping issues open that don't have any realistic chance of being addressed.
  • close bugs as "won't fix" if there is no cost-benefit balance. It's not that we don't care about users who are affected by an issue but, for example, if the fix is so involved that we risk regressions for many, fixing is not a reasonable choice.

Otherwise the normal rules apply:

  • 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
  • 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.

Issues assigned to you

Issues assigned to feature areas but without owner

Other issues

  • ensure we don't have any issues assigned to people who are no longer on the team @kieferrm

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