search

microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
160.6k stars 28.14k forks source link

February Iteration Plan #2616

Closed egamma closed 8 years ago

egamma commented 8 years ago

February is our last full iteration before we start the end game for the Build 2016 milestone at the end of March.

We made good progress in the areas such as accessibility and localization, but more work needs to happen. Therefore we arrived at the following themes for February:

For more information about our development process please refer to the development process page.

Endgame Schedule

Monday, Feb 22
Mark Description
:runner: work in progress
:hand: task is blocked
:muscle: stretch goal for this iteration

Feedback

Issues to address feedback from the community:

This section lists items to reduce our engineering debt:

We continuously have to adopt components which we require:

This section lists several engineering/development items that the team identified:

profiler-bg commented 8 years ago

I'm confused by all the January mentions. Feb schedule should be end of Feb, should it not? Is it due to using the Jan file as template?

chrisdias commented 8 years ago

@profiler-bg yes, this is a work in progress :)

piyushchauhan2011 commented 8 years ago

:+1:

gilvandovieira commented 8 years ago

:+1: thanks

zethon commented 8 years ago

VisualCodeFolding

brennanMKE commented 8 years ago

I cannot wait for code folding. I have been working heavily in VS Code over the past month and with large source files it is so helpful to collapse code to make it more readable.

StfBauer commented 8 years ago

:+1:

nyn3x commented 8 years ago

:+1:

BazIdle commented 8 years ago

Not sure if I should address this here, but: Any plans on adopting new stuff from OmniSharp ?

OmniSharp crashes are still present for me in the latest (recent, "January"-one) build.

As far as I understand (from OmniSharp issuetracker), they had a lot of major changes recently.

Would love to know an insight ;)

leeroya commented 8 years ago

Brilliant Thanks. cant wait.

egamma commented 8 years ago

@BazIdle OmniSharp will continue to move forward and it is now in the best hands (the team that also works on Roslyn). The work on Omnisharp for vscode is now tracked in https://github.com/OmniSharp/omnisharp-vscode.

Your issue from above is now also tracked there OmniSharp/omnisharp-roslyn#371.

FYI @DustinCampbell

BazIdle commented 8 years ago

@egamma Thanks for the info

Figbash commented 8 years ago

@egamma @BazIdle Sorry for bugging you here, but I and many people I know have been struggling with this issue since .10.3, is there any chance someone would be willing to look at it for this iteration? I have multiple projects that do it and would love to help someone track it down. There doesn't seem to be any interest in omnisharp-vscode, our issues have been there since December with no chatter. VSCode cannot be used for us in this state, and I really want to be able to upgrade! https://github.com/OmniSharp/omnisharp-vscode/issues/6 this is my bug for the same issue.

DustinCampbell commented 8 years ago

Sorry @Figbash for not commenting over at https://github.com/OmniSharp/omnisharp-vscode/issues/6. We're in the middle of a bunch of work to move the extension to a new version of OmniSharp that's also in progress. Once we get over that hurdle, I'll dig deeper into your issue.

Figbash commented 8 years ago

@DustinCampbell Thank you for letting me know. No worries about commenting I just wanted to make sure it wasn't lost in the shuffle.

Nimzozo commented 8 years ago

:coffee:

penguin020 commented 8 years ago

This is just great that you make this so transparent. Thanks.