-
Notifications
You must be signed in to change notification settings - Fork 34.5k
Closed
Labels
plan-itemVS Code - planned item for upcomingVS Code - planned item for upcoming
Milestone
Description
During October we groom our open issues.
Preparation
- review issue types
- review feature areas
- review issue grooming
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
- @aeschli
- @alexandrudima
- @alexr00
- @bowdenk7
- @bpasero
- @chrisdias
- @chrmarti
- @Chuxel
- @dbaeumer
- @deepak1556
- @egamma
- @fiveisprime
- @gregvanl
- @isidorn
- @joaomoreno
- @jrieken
- @kieferrm
- @misolori
- @mjbvz
- @octref
- @rebornix
- @RMacfarlane
- @roblourens
- @sana-ajani
- @sandy081
- @sbatten
- @stevencl
- @Tyriar
- @weinand
Issues assigned to feature areas but without owner
-
api
-
api-finalization
-
api-proposal
-
breadcrumbs
-
callhierarchy
-
color-palette
-
comments
-
config
-
context-keys
-
css-less-scss
-
debug
-
debug-console
-
dialogs
-
diff-editor
-
dropdown
-
editor
-
editor-autoclosing
-
editor-autoindent
-
editor-bracket-matching
-
editor-clipboard
-
editor-code-actions
-
editor-code-lens
-
editor-color-picker
-
editor-columnselect
-
editor-commands
-
editor-comment-commands
-
editor-contrib
-
editor-core
-
editor-drag-and-drop
-
editor-error-widget
-
editor-find
-
editor-folding
-
editor-hover
-
editor-ime
-
editor-indent-guides
-
editor-input
-
editor-insets
-
editor-minimap
-
editor-multicursor
-
editor-parameter-hints
-
editor-render-whitespace
-
editor-rendering
-
editor-scrollbar
-
editor-symbols
-
editor-textbuffer
-
editor-theming
-
editor-wordnav
-
editor-wrapping
-
emmet
-
error-list
-
explorer-custom
-
extension-host
-
extensions
-
extensions-development
-
file-decorations
-
file-encoding
-
file-explorer
-
file-glob
-
file-guess-encoding
-
file-io
-
file-watcher
-
font-rendering
-
formatting
-
git
-
git-merge
-
gpu
-
grammar
-
grid-view
-
html
-
i18n
-
icon-brand
-
icons-product
-
install-update
-
integrated-terminal
-
integrated-terminal-conpty
-
integrated-terminal-winpty
-
integration-test
-
intellisense-config
-
ipc
-
issue-bot
-
issue-reporter
-
javascript
-
json
-
keybindings
-
keybindings-editor
-
keyboard-layout
-
L10N
-
label-provider
-
languages-basic
-
languages-diagnostics
-
languages-guessing
-
layout
-
list
-
log
-
markdown
-
marketplace
-
menus
-
merge-conflict
-
outline
-
output
-
perf
-
perf-bloat
-
perf-startup
-
php
-
portable-mode
-
proxy
-
quick-pick
-
references-viewlet
-
release-notes
-
remote
-
rename
-
samples
-
scm
-
screencast-mode
-
search
-
search-replace
-
semantic-coloring
-
settings-editor
-
shared-process
-
simple-file-dialog
-
smart-select
-
smoke-test
-
snap
-
snippets
-
splitview
-
suggest
-
tasks
-
telemetry
-
themes
-
titlebar
-
tokenization
-
trackpad/scroll
-
tree
-
typescript
-
unit-test
-
uri
-
ux
-
variable-resolving
-
VIM
-
vscode-build
-
vscode-website
-
web
-
webview
-
workbench-cli
-
workbench-diagnostics
-
workbench-dnd
-
workbench-editor-grid
-
workbench-editors
-
workbench-electron
-
workbench-feedback
-
workbench-history
-
workbench-hot-exit
-
workbench-launch
-
workbench-link
-
workbench-multiroot
-
workbench-notifications
-
workbench-os-integration
-
workbench-rapid-render
-
workbench-run-as-admin
-
workbench-state
-
workbench-status
-
workbench-tabs
-
workbench-touchbar
-
workbench-views
-
workbench-welcome
-
workbench-window
-
workbench-zen
-
workspace-edit
-
workspace-symbols
-
zoom
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 upcomingVS Code - planned item for upcoming