Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

April Issue Grooming - review, categorization, assignment #24059

Closed
16 of 19 tasks
egamma opened this issue Apr 6, 2017 · 3 comments
Closed
16 of 19 tasks

April Issue Grooming - review, categorization, assignment #24059

egamma opened this issue Apr 6, 2017 · 3 comments
Assignees
Labels
engineering VS Code - Build / issue tracking / etc. plan-item VS Code - planned item for upcoming

Comments

@egamma
Copy link
Member

egamma commented Apr 6, 2017

During April we want to get the bug count down. As a first step we will review the assigned issues. During the review pass please make sure to:

  • close obsolete/fixed issues
  • each issue needs a type label, that is one of: Bug, Feature-Request, Debt, Needs more Info, Question, Under-Discussion, upstream:
    • Bug - the implementation of a feature is not correct
    • Feature-Request - request to change the proper implementation of a feature or a request for a new feature that needs to be implemented.
    • Under Discussion - not decided whether the issue is a bug or feature
    • Debt - improve the implementation/architecture
    • Needs more info - not possible to assing a type label due to missing information
    • Question - we should direct questions to SO
    • upstream - an issue used to track an issue in an upstream component
    • 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 April to the April milestone
  • issues that the community can take up should be labeled as help-wanted
  • feature requests that should be implemented as extensions should be labeled extensions-candidate and be closed

Finding issues with no Type label

Use the following filter an replace the assignee:

is:open is:issue -label:bug -label:feature-request -label:debt -label:under-discussion assignee:YOURNAME -label:question -label:upstream -label:plan-item -label:"needs more info"

Tracking:

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

@egamma egamma added the plan-item VS Code - planned item for upcoming label Apr 6, 2017
@bpasero
Copy link
Member

bpasero commented Apr 6, 2017

just a usability nit, I find labels without background a bit weird:

image

@kieferrm kieferrm mentioned this issue Apr 6, 2017
15 tasks
@aeschli
Copy link
Contributor

aeschli commented Apr 6, 2017

image

Hard to tell which issues don't have a label yet.

@egamma
Copy link
Member Author

egamma commented Apr 6, 2017

OKi, changed the background to SlateGrey

@egamma egamma changed the title April - Bug review, categorization, assignment April Issue Grooming - review, categorization, assignment Apr 7, 2017
@kieferrm kieferrm added the engineering VS Code - Build / issue tracking / etc. label Apr 24, 2017
@egamma egamma closed this as completed Jun 29, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
engineering VS Code - Build / issue tracking / etc. plan-item VS Code - planned item for upcoming
Projects
None yet
Development

No branches or pull requests

4 participants