Vscode: June Iteration Plan

[egamma]

This plan captures what we work on during June and will ship early July.

We arrived at the following themes for June:

• Remove the most requested adoption blockers.
• Make the repository with the Monaco/standalone editor available.
• Improve the getting started experience

The June Test Plan items are created as issues get closed.

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

Schedule

• June 27 Code freeze for the endgame June
• June 29 Endgame done

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

Monday, Jun 27

• [x] Code freeze at end of day

  Tuesday, Jun 28

• [x] Test plan input done at 8am Zurich time

• [x] Test plan ready
• [x] Test build done

• [x] Testing

  Wednesday, Jun 29

• [x] Testing

• [x] Fixing

  Thursday, Jun 30

• [x] Fixing

• [x] Run OSS tool
• [x] Verification

• [x] Update release notes

  Friday, Jul 1

• [x] Add shrink-wrap files

• [x] Run OSS tool after merging shrinkwrap findings - @weinand
  
  
  
  • [x] Check new OSS usage is entered into the tool - @kieferrm
  
  
• [x] Fixing (only critical bugs)
• [x] Translation input - @dbaeumer
• Smoketest
  
  
  
  • [x] Windows - @ramya-rao-a
  
  
  • [x] OS X - @chrmarti
  
  
  • [x] Linux - @Tyriar
  
  
• [x] All release notes updated
• Satellite modules ready, version updated, smoke tested
  
  
  
  • [x] vscode @bpasero
  
  
  • [x] yo generator @aeschli
  
  
  • [x] vsce @joaomoreno
  
  
  • [x] node debug @weinand
  
  
• [x] Pause scheduled insider builds @bpasero

• When done fixing/verifying

  • [x] Trigger insider build and publish it manually @kieferrm
    

    Monday, Jul 4

• US Holiday

• [x] Tag 1.3 build @zurich
• [x] Announce announce master is open for business @zurich
• [x] All issues verified
• [x] Acknowledge pull requests in release notes - All
• [x] Review docs

• Review Docs for coverage of new features. Tracked in Microsoft/vscode-docs#374

  Tuesday, Jul 5

• [ ] Polish release notes (Redmond)

• [ ] Inbox review #8753

• [x] Publish Insider with hand-picked and reviewed candidate fixes

  Thursday/Friday, Jul 7/8

• [ ] Publish to stable

• [ ] Enable scheduled insider builds
  

  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:

• [x] Extract the MarkDown editing support into an extension #6106 @kieferrm
  
  
  
  • [x] Test: Markdown extension , #7945
  
  
  • [x] Release Notes
  
  
• [x] Extract CSS/LESS/SASS and JSON into an extension @aeschli
  
  
  
  • [x] Test the VS Code CSS/LESS and SCSS Mode, #8212
  
  
  • [x] Test the VS Code JSON Mode, #8208
  
  
  • [x] Release Notes
  
  
• [x] Ensure extension install count is properly updated @joaomoreno
• [x] Monaco Editor - make the CSS/LESS/SASS and JSON language services available in the editor @aeschli
  
  
  
  • [x] CSS/LESS and SCSS in the Monaco editor, #8213
  
  
  • [x] JSON in the monaco editor, #8210
  
  
  • [x] Release Notes
  
  

Feedback

Issues to address feedback from the community:

• [x] UI - Tabs - visualize tabs #224 @bpasero @isidorn
  
  
  
  • [x] Tabs, #7854
  
  
  • [x] Drag and Drop editors and tabs, #7852
  
  
  • [x] Release Notes
  
  
• [x] UI - Add an integrated terminal #143 @Tyriar
  
  
  
  • [x] Test: Integrated Terminal (June), #8222
  
  
  • [x] Test Open in Terminal settings for OS X, #8198
  
  
  • [x] Release Notes
  
  
• [x] Editor - Support that the Monaco editor can be consumed standalone #446 @alexandrudima
  
  
  
  • [x] Standalone Editor, #8229
  
  
  • [x] Release Notes
  
  
• [x] Editor - Find does not match multi-line regex strings #313 @alexandrudima
  
  
  
  • [x] Multiline find, #8230
  
  
  • [x] Release Notes
  
  
• [x] :runner: Editor - Indent guides #2192 @alexandrudima @aeschli
  
  
  
  • [x] Indent guides, #8232
  
  
  • [x] Release Notes
  
  
• [x] UI - Add an error list panel #6679 @sandy081
  
  
  
  • [x] Tests for Problems view, #7601
  
  
  • [x] Release Notes
  
  
• [x] UI - Support global replace #7602 @sandy081
  
  
  
  • [x] Tests for Global Replace, #8184
  
  
  • [x] Release Notes
  
  
• [x] Make the debug toolbar moveable #4580
  
  
  
  • [x] Test draggable debug toolbar, #7815
  
  
  • [x] Release Notes
  
  
• :runner: Debug - Support Live Reloading Scenarios #6930 @weinand
  
  
  
  • [x] Make source map handling asynchronous #8162
  
  
• [x] API - Support to contribute a command to the editor action bar and context menus @jrieken
  
  
  
  • [x] Test menu contributions, #8197
  
  
  • [x] Release Notes
  
  
• [x] Emmet - Expose more emmet features #7909 #8155 @egamma
  
  
  
  • [x] Test new emmet features #8207
  
  
  • [x] Release Notes
  
  
• [x] API - Decorations support before and after attachments @aeschli
  
  
  
  • [x] Test #8268
  
  
  • [x] Release Notes
  
  
• [x] Add debugging attach support using a Picker UI to VS Code #6569 @weinand, @isidorn
  
  
  
  • [x] Test "attach to process" picker and author another variable that is bound to a command, #8196
  
  
  • [x] Release Notes
  
  
• [x] API - expose theme id in webview, #7589
  
  
  
  • [x] Test theme hint in previewHtml, #8190
  
  
  • [x] Release Notes
  
  
• [x] API - command to open any file, #566
  
  
  
  • [x] Test vscode.open API command, #8195
  
  
  • [x] Release Notes
  
  
• [x] API - derive Uris from existing ones, #6678
  
  
  
  • [x] Test new Uri#with API, #8192
  
  
  • [x] Release Notes
  
  
• [x] Editor - suggestions for commands ids when authoring keybindings, #7185
  
  
  
  • [x] Suggestions for command ids in keybinding.json, #8191
  
  
  • [x] Release Notes
  
  
• [x] Editor - alternative JavaScript grammar
  
  
  
  • [x] Test the Atom JavaScript grammar, #8204
  
  
  • [x] Release Notes
  
  

Engineering

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

• [x] Improve in product extension management UI #637 - @joaomoreno
  
  
  
  • [x] Extensions UI, #8215
  
  
  • [x] Release Notes
  
  
• [x] Improve extension recommendations - @joaomoreno
  
  
  
  • [x] ???test???
  
  
  • [x] Release Notes
  
  
• [x] vsce - add version check to vsce and remind user to update to a newer version @joaomoreno
• [x] Debug - Expand protocol to cover VS scenarios protocol extensions @weinand
  
  
  
  • [x] Release Notes
  
  
• [x] Surface new debug protocol additions in VS Code @isidorn, @weinand
  
  
  
  • Add UI for editing variables #7744
  
  
  • [x] Test setting variable values, #7812
  
  
  • [x] Release Notes
  
  
  • Show variable type on hover #8040
  
  
  • [x] Test 'Variable Type Hover', #8199
  
  
  • [x] Release Notes
  
  
  • UI support for TimeTravel Debugging #7652
  
  
  • [x] Test 'UI support for TimeTravel Debugging', #8200
  
  
  • [x] Release Notes
  
  

Explorations

• [x] TypeScript - Explore project level errors/warnings @dbaeumer

  • [x] Test 'Explore project wide builder for TS', #8203
    

    Deferred

• Support to increase the font size used by IntelliSense #2465

• :hand: TS Adoption - Intellisense on nodejs app files with no extension #7446
• API - Expose support to edit JSON settings #1396
• Adopt JSON edit support to update file association settings
• :hand: Linux - Continue to push for code signing #2973 @tyriar
• Linux - Hygiene work on the packages (names, dependencies, size reduction) @tyriar
  

  Bugs

Bugs assigned to the current milestone:

• vscode

[glen-84]

We arrived at the following themes for May:

Should be June. =)

TypeScript/JavaScript - Explore project level errors/warnings

Is this just "give tslint etc. the folder name instead of the file name", as opposed to VS Code actually keeping track of errors/warnings during an "indexing" process (where each file is processed separately)?

[egamma]

@glen-84 thanks for catching the typo.

Is this just "give tslint etc. the folder name instead of the file name", as opposed to VS Code actually keeping track of errors/warnings during an "indexing" process (where each file is processed separately)?

This is an investigation to add scalable project level errors to the typescript language service and tsServer. This is independent of tslint.

[niieani]

Fantastic job guys. Honestly, you're developing faster than a lightning! Thanks a lot for making the best IDE out there.

🏆 🎆 💃

[yeluoqiuzhi]

thanks. good job

[egamma]

Shipped 1.3 closing