Skip to content

Iteration Plan for February 2019 #68293

Description

@kieferrm

This plan captures our work in February. This is a 4 week iteration, and we will ship our February Update in in early March. We'll continue work we started in the previous iteration, and we started to pick up items from our roadmap.

Endgame

  • February 25, 2019: Code freeze for the endgame (Zurich freezes on February 22)
  • March 1, 2019: Endgame done

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

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

Workbench

UX

Editor

Tasks

Languages

LSP

JavaScript/TypeScript

CSS/HTML

Debug

Debug Adapter Protocol

Extension Contributions

Extensions

API

Exploration

Engineering

Documentation


Deferred Items

Activity

  1. maciejw commented on Feb 10, 2019

    @maciejw

    you mean Electron 4.0 upgrade released on stable channel!? finally in my company we will be able to upgrade from 1.25.1 ❤👌

  2. svipas commented on Feb 11, 2019

    @svipas
    Contributor

    Maciej Warszawski (@maciejw) Just curious, why you're still using 1.25.1 version? And how Electron 4 is related to this? Current VS Code version uses Electron 3.1.3 which is latest from v3.x.

  3. maciejw commented on Feb 11, 2019

    @maciejw

    @svipben because of this #56644, 40 seconds startup is too painful :)

  4. svipas commented on Feb 11, 2019

    @svipas
    Contributor

    Thanks, didn't know about this issue. Good news there are already exploration builds with Electron 4 which you can download and use ✨

  5. maciejw commented on Feb 11, 2019

    @maciejw

    I know, are they stable enough though ;)

  6. changed the title [-]Iteration Plan for February 2019 [DRAFT][/-] [+]Iteration Plan for February 2019[/+] on Feb 12, 2019
  7. dpen2000 commented on Feb 14, 2019

    @dpen2000

    Can this (and hopefully future iteration plans) be pinned so they show up above issue list? See https://github.com/proxy/help.github.com/articles/pinning-an-issue-to-your-repository/

  8. egamma commented on Feb 18, 2019

    @egamma
    Member

    David Pendray (@dpen2000) thanks for the suggestion. I've pinned the issue so that we can try this out.

  9. JCMais commented on Feb 27, 2019

    @JCMais

    is just me or the dpi was really improved recently? Was that something worked on for this release? Or I'm just imagining things (using latest Insiders on Win10)

  10. kieferrm commented on Mar 7, 2019

    @kieferrm
    MemberAuthor

    Shipped.

  11. locked and limited conversation to collaborators on Apr 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

iteration-planVS Code - Upcoming iteration plan

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions