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

February Iteration Plan #2616

Closed
92 of 97 tasks
egamma opened this issue Feb 1, 2016 · 17 comments
Closed
92 of 97 tasks

February Iteration Plan #2616

egamma opened this issue Feb 1, 2016 · 17 comments
Assignees
Labels
iteration-plan VS Code - Upcoming iteration plan
Milestone

Comments

@egamma
Copy link
Member

egamma commented Feb 1, 2016

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:

  • Continue the work on accessibility, localization.
  • Reduce adoption blockers - the item we want to tackle is support for Code Folding, the most voted for feature request, Issue Enable code folding and collapsing #105.
  • Reduce the engineering debt.
  • Respond to feedback and try to address as many issues as possible.

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

Endgame Schedule

Monday, Feb 22
  • Code freeze at end of day
Tuesday
  • Test build done
  • Testing
Wednesday
Thursday
  • Fixing
  • Verification
Friday
Monday, Feb 29
Monday, March 7
  • Release stable channel

Plan Items

Mark Description
🏃 work in progress
task is blocked
💪 stretch goal for this iteration

Feedback

Issues to address feedback from the community:

Debt Items

This section lists items to reduce our engineering debt:

Adoptions

We continuously have to adopt components which we require:

Engineering Items

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

Testers

@egamma egamma added the iteration-plan VS Code - Upcoming iteration plan label Feb 1, 2016
@egamma egamma self-assigned this Feb 1, 2016
@egamma egamma added this to the Feb 2016 milestone Feb 1, 2016
@egamma egamma changed the title March Iteration Plan February Iteration Plan Feb 1, 2016
@profiler-bg
Copy link

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
Copy link
Member

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

@piyushchauhan2011
Copy link

👍

@gilvandovieira
Copy link

👍 thanks

@zethon
Copy link

zethon commented Feb 9, 2016

#VisualCodeFolding

@brennanMKE
Copy link

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
Copy link

StfBauer commented Feb 9, 2016

👍

1 similar comment
@nyn3x
Copy link

nyn3x commented Feb 9, 2016

👍

@BazIdle
Copy link

BazIdle commented Feb 9, 2016

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
Copy link

leeroya commented Feb 10, 2016

Brilliant Thanks. cant wait.

@egamma
Copy link
Member Author

egamma commented Feb 10, 2016

@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
Copy link

BazIdle commented Feb 10, 2016

@egamma Thanks for the info

@Figbash
Copy link

Figbash commented Feb 20, 2016

@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!
dotnet/vscode-csharp#6 this is my bug for the same issue.

@DustinCampbell
Copy link
Member

Sorry @Figbash for not commenting over at dotnet/vscode-csharp#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
Copy link

Figbash commented Feb 21, 2016

@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
Copy link

Nimzozo commented Feb 28, 2016

@penguin020
Copy link

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

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
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