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.

Sign up for GitHub

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

Jump to bottom

November Issue Grooming - review, categorization, assignment #38209

Closed
13 of 18 tasks
egamma opened this issue Nov 13, 2017 · 2 comments
Closed
13 of 18 tasks

November Issue Grooming - review, categorization, assignment #38209

egamma opened this issue Nov 13, 2017 · 2 comments
Assignees
@egamma @rebornix @kieferrm
Labels
plan-item VS Code - planned item for upcoming
Milestone
November 2017

Comments

@egamma
Copy link
Member

egamma commented Nov 13, 2017 •
edited
Loading

During November we want to improve our issue management. 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 November to the November 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

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 Nov 13, 2017
@egamma egamma added this to the November 2017 milestone Nov 13, 2017
@alexdima alexdima self-assigned this Nov 13, 2017
@chrmarti chrmarti self-assigned this Nov 13, 2017
@rebornix rebornix self-assigned this Nov 13, 2017
@kieferrm kieferrm mentioned this issue Nov 14, 2017
Closed
25 tasks
@bpasero bpasero self-assigned this Nov 14, 2017
@innerlee innerlee mentioned this issue Nov 17, 2017
Closed
@bpasero bpasero removed their assignment Nov 17, 2017
@bpasero
Copy link
Member

bpasero commented Nov 17, 2017

Here is my template for closing issues that are out of scope:

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!

@rebornix rebornix assigned rebornix and unassigned rebornix Nov 20, 2017
@chrmarti chrmarti removed their assignment Dec 1, 2017
@alexdima alexdima removed their assignment Dec 4, 2017
@alexdima
Copy link
Member

November is done.

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@egamma egamma

@rebornix rebornix

@kieferrm kieferrm

Labels
plan-item VS Code - planned item for upcoming
Projects
None yet
Milestone
November 2017
Development

No branches or pull requests
6 participants
@egamma @rebornix @bpasero @kieferrm @alexdima @chrmarti