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

Iteration Plan for August 2019 #78844

Closed
25 of 37 tasks
kieferrm opened this issue Aug 10, 2019 · 11 comments
Closed
25 of 37 tasks

Iteration Plan for August 2019 #78844

kieferrm opened this issue Aug 10, 2019 · 11 comments
Assignees
Labels
iteration-plan VS Code - Upcoming iteration plan
Milestone

Comments

@kieferrm
Copy link
Member

kieferrm commented Aug 10, 2019

This plan captures our work in August. This is a 4-week iteration. We will ship our August Update in early September.

Although this is the last of the Summer vacation months for us, good work is coming your way. With our work on Custom Editors and the settings sync provider API exploration we continue to pushing the boundaries of what extensions can provide. We also work on the overall user experience with items such as improved minimap and multi-select in custom tree views, and we continue our journey to better performance with reworking tokenization. See below for all the details.

Endgame

  • August 26, 2019: Endgame begins
  • August 30, 2019: Endgame done

The endgame details for this iteration are tracked in #79792.

Plan Items

Below is a summary of the top level plan items.

Legend of annotations:

Mark Description
🏃 work in progress
blocked task
💪 stretch goal for this iteration
🔴 missing issue reference
🔵 more investigation required to remove uncertainty
under discussion within the team

UX

Workbench

Editor

Languages

JavaScript/TypeScript

LSP

CSS/HTML/JSON

Debug

API

Extension Contributions

Engineering


Deferred Items

@KevinWuWon
Copy link

Looking forward to the Custom Editors API!

@ackvf
Copy link

ackvf commented Aug 12, 2019

Awesome, can't wait for being able to copy deleted text from diff. Hurray 🎉 🎉 #8226

@jletey
Copy link

jletey commented Aug 12, 2019

@kieferrm Here is the correct link to #78889: https://github.com/microsoft/vscode/issues/78889

@kieferrm kieferrm added iteration-plan VS Code - Upcoming iteration plan and removed iteration-plan-draft VS Code - Upcoming iteration plan (Draft) labels Aug 12, 2019
@kieferrm kieferrm changed the title Iteration Plan for August 2019 [DRAFT] Iteration Plan for August 2019 Aug 12, 2019
@kieferrm kieferrm pinned this issue Aug 12, 2019
@equinusocio
Copy link

equinusocio commented Aug 16, 2019

Please, please decrease the arrow size for code folding 😂 😂

Screenshot 2019-08-16 at 13 51 17

@aeschli
Copy link
Contributor

aeschli commented Aug 16, 2019

@equinusocio Please file a separate issue with your settings.

@DiamondYuan
Copy link
Contributor

As a community contributor, I also hope to fix some issues and complete some feature.

@FFY00
Copy link

FFY00 commented Aug 19, 2019

@DiamondYuan you could look into #72298 if you have time. The official team doesn't want to spend time on it but is something that would really help the community.

@tristan957
Copy link

@FFY00 in the issue the team specifically asks you to point out the lines that need changing. I am sure someone would like to fix it, but you haven't responded in 8 days with the answer.

@jregistr
Copy link

Option for merging single child directories with parent in the Explorer #41627

🤞 This is certainly my most anticipated feature in this release cycle. This is such a must for anyone in the JVM community.

@FFY00
Copy link

FFY00 commented Aug 21, 2019

@FFY00 in the issue the team specifically asks you to point out the lines that need changing. I am sure someone would like to fix it, but you haven't responded in 8 days with the answer.

I am not a JavaScript developer, still I have spent hours trying to fix this. That's why I opened the issue. If I knew how to fix it I would just open a pull request. The vscode team knows the codebase and given that this is not a difficult issue I am pretty sure they would be able to track down the source easily. I have projects that actually need my attention, I can't keep wasting time here just because the vscode team doesn't want to help.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
iteration-plan VS Code - Upcoming iteration plan
Projects
None yet
Development

No branches or pull requests

12 participants