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

2021 Issues Cleanup - review, categorization, assignment #134380

Closed
31 of 89 tasks
egamma opened this issue Oct 4, 2021 · 0 comments
Closed
31 of 89 tasks

2021 Issues Cleanup - review, categorization, assignment #134380

egamma opened this issue Oct 4, 2021 · 0 comments
Assignees
@egamma @kieferrm
Labels
plan-item VS Code - planned item for upcoming
Milestone
November 2021

Comments

@egamma
Copy link
Member

egamma commented Oct 4, 2021 •
edited by hediet
Loading

During October we cleanup our open issues.

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 across the VS Code repositories 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. 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 cleanup in our satellite repositories.

Issues assigned to you

Other issues

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

Satellite repositories
@egamma egamma added the plan-item VS Code - planned item for upcoming label Oct 4, 2021
@egamma egamma added this to the October 2021 milestone Oct 4, 2021
@egamma egamma changed the title 2021 Issue Grooming - review, categorization, assignment 2021 Issues Cleanup - review, categorization, assignment Oct 4, 2021
@kieferrm kieferrm mentioned this issue Oct 10, 2021
Closed
5 tasks
@kieferrm kieferrm mentioned this issue Nov 7, 2021
Closed
82 tasks
@egamma egamma modified the milestones: October 2021, November 2021 Nov 8, 2021
@egamma egamma closed this as completed Jan 5, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Feb 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@egamma egamma

@kieferrm kieferrm

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

No branches or pull requests
2 participants
@egamma @kieferrm