Vscode: April Iteration Plan

Created on 3 Apr 2016  路  12Comments  路  Source: microsoft/vscode

While watching the community feedback on 1.0, we have already started to work on the next update. We will continue to ship monthly. This plan captures what we work on during April and will ship early May.

We arrived at the following themes for April:

  • Ramp up the work on the next major version.
  • Do some explorations.
  • Reduce engineering debt in vscode and the primary extensions which the team maintains (vscode-eslint, vscode-jshint, vscode-tslint, vscode-jscs).

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

The April Test Plan is in progress.

Schedule

The goal is to make the April update available by the following dates.

End game dates (we end an iteration with an endgame)

Monday, Apr 25
  • [x] Code freeze at end of day

    Tuesday, Apr 26
  • [x] Test build done

  • [x] Testing
  • [x] Push to insider channel

    Wednesday, Apr 27
  • [x] Testing

  • [x] Fixing
  • [x] Run OSS tool

    Thursday, Apr 28
  • [x] Fixing

  • [x] Verification

    Friday, Apr 29
  • [x] Fixing

  • [x] Smoketest

    • [x] Windows @bpasero

    • [x] OS X @jrieken

    • [x] Linux @aeschli

  • [x] All release notes updated

    • [x] @aeschli

    • [x] @alexandrudima

    • [x] @bpasero

    • [x] @jrieken

    • [x] @joaomoreno

    • [x] @isidorn

    • [x] @egamma

  • [x] Acknowledge pull requests in release notes: @bpasero
  • [x] All issues verified
  • [x] Satellite modules ready, version updated, smoke tested

    • [x] vscode @bpasero
    • [x] yo generator @aeschli
    • [x] vsce @joaomoreno
    • [x] Debug adapter @weinand
      Monday, May 2
  • [x] Push to insider channel

    Monday, May 9
  • [x] Release stable channel

    Plan Items

| Mark | Description |
| --- | --- |
| :runner: | work in progress |
| :hand: | task is blocked |
| :muscle: | stretch goal for this iteration |

Debt Items

This section lists items to reduce our engineering debt:

  • [ ] Community: Support Pull Requests for the Wiki @Tyriar
    #### Feedback

Issues to address feedback from the community:

  • [ ] UI: Start implementing support for tabs #224 @bpasero
  • [ ] UI:
    #4650 @bpasero
  • [x] UI: Add command to reopen last closed editor #3989 @Tyriar

    • Test #5586

    • [x] Release notes

  • [x] I18N: Command palette match support for non-ascii characters #4691 @bpasero
  • [x] Provide an option to stop scrolling revealing active file in explorer #3062 @bpasero

    • Test: #5329

  • [x] Emmet: support to disable expansion on TAB #5756 @egamma
  • [x] I18N: Support to filter the Command Palette by English name #4679 @bpasero

    • Test: #5764

  • [x] API: Add support for internal links in previewHtml #3676 @jrieken

    • Test: #5747

  • [x] API: Provide API to open a new folder #58 @bpasero
  • [x] Git: Commit in the command palette #4471 @joaomoreno

    • Test: #5766

  • [x] Linux: Support running vscode with sudo permissions #3068 @tyriar

    • Test #5062

    • [x] Release notes

  • [x] Linux: Include CLI in Linux zip archive and support custom install locations #4426 @tyriar

    • Test #4985

    • [x] Release notes

  • [x] Linux: Notify user when a new update is available @joaomoreno

    • Test: #5757

  • [x] Debug - Data inspection support for ES6 objects (sets, maps, generators) Microsoft/vscode-node-debug#51, Microsoft/vscode-node-debug#41 @weinand

    • Test #4949

    • [x] Release notes

  • Address feedback received on primary extensions

    • [x] eslint @dbaeumer

    • Test: #5654

    • [x] tslint @egamma

    • Test: #5758

    • [x] jshint @kieferrm

    • Test: #5759

    • [x] jscs: @chrisdias

Engineering

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

  • [x] Debug - Paging support for stack frames #4792 @weinand @isidorn

    • Test #4819

    • [x] Release notes

  • [x] Debug - Data inspection of large objects for Node v4.x and v5.x

    • Test: #4951

      Microsoft/vscode-node-debug#11 @weinand

    • Test #4951

    • [x] Release notes

  • [x] Debug - Data inspection support for large strings and objects with getters Microsoft/vscode-node-debug#14 @weinand

    • Tests #4952, #4957

    • [x] Release notes

  • [x] Implement version 2 of the language service protocol addressing feedback from version 1 @dbaeumer
  • [x] Adopt - Electron 0.37.x #4199 @bpasero

Initial investigations/explorations

  • :runner: UI - Improve extension installation UI #637 @joaomoreno
  • :runner: UI - Add an integrated terminal #143 @Tyriar
  • [x] Debug - C++ debug scenario to enable additional debug views (e.g. memory view) @isidorn
  • [x] Debug - Support skipping code when stepping #4798 @weinand

    • Test #4954

    • [x] Release notes

  • [x] API - Use web view for html preview part #2414 @jrieken

    • Test: #5748

      Deferred from April


Deferred to May

  • [ ] :runner: Debug - Support for dynamically generated source maps #4492 @weinand

    • recent change of SystemJS broke dynamic source map support; deferred to May release

    • Test #4953

    • [ ] Release notes

      Bugs


This section includes bug queries for the vscode related repositories:

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

iteration-plan

Most helpful comment

Thank you! thank you for all the hard work and efforts to make VSCode amazing and it really is amazing, it's by far my favorite editor now. <3

All 12 comments

I'm surprised to not see https://github.com/Microsoft/vscode/issues/1703 here, it has April milestone assigned, I consider it a pretty important bug and it's been around since December....

@felixfbecker #1703 is listed under the Bugs section.

@weinand My bad

Just for the sake of clarity, the April release referred to here would be _after_ 1.0 is released, correct?

Just for the sake of clarity, the April release referred to here would be after 1.0 is released, correct?

Correct, the April release will be available early May and the 1.0 release really soon.

I'm just wondering if it doesn't make sense to refer to it as the May release, as it will be released in May and not April. I've seen some confusion around this before.

Thank you! thank you for all the hard work and efforts to make VSCode amazing and it really is amazing, it's by far my favorite editor now. <3

Has the new insider release been published?

@else yeah, I just got the 1.1.0 Insider release yesterday

Hmm, I tried downloading it from here but that version tells me its build date is 26th of April.

It would be nice if you could mention #4702 in the release notes :)

Closing - stable is updated

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lukehoban picture lukehoban  路  3Comments

biij5698 picture biij5698  路  3Comments

curtw picture curtw  路  3Comments

v-pavanp picture v-pavanp  路  3Comments

trstringer picture trstringer  路  3Comments