Skip to content

Iteration Plan for March 2024 #206739

Description

@kieferrm

This plan captures our work in March. This is a 5-week iteration. We will ship in early April.

Endgame

  • March 25, 2024: Endgame begins
  • March 28, 2024: Endgame done

The endgame details for this iteration are tracked here.

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
⬛ a large work item, larger than one iteration

Accessibility

Workbench

Code Editor

Search

Authentication

Notebook Editor

Jupyter Notebooks

WebAssembly Support

Issue Reporter

Languages

Python

TypeScript

Terminal

Source Control

Testing

Debug

Debug Adapter Protocol

API

Extensions

Extension Contributions

Engineering

Electron


Deferred

Activity

  1. gjsjohnmurray commented on Mar 4, 2024

    @gjsjohnmurray
    Contributor

    Disappointment again that neither #59921 nor #73524 are listed, and that Andrea Mah (@andreamah)'s only item (#204853) involves polishing a recently-added feature (Quick Search, specifically its Previewing capability) that is still not available (polished or unpolished) to our userbase (pinging Brett Saviano (@isc-bsaviano)) because those two proposed APIs have remained unfinalized for more than 5 years now.

  2. isc-bsaviano commented on Mar 4, 2024

    @isc-bsaviano

    As I've explained in the past, our company is migrating from a legacy proprietary IDE to VS Code. That legacy IDE only used virtual file systems, which means that most of our user base will want to continue doing so in VS Code. Users have expressed confusion as to why they must jump through hoops to access these features, and it is certainly a barrier to migration for some. Everyone who has activated the proposed APIs has been happy with them, so from their perspective there is no reason why the APIs can't be finalized. Even if there are minor concerns about them within the VS Code core team, it would be a big boost for end users like us to have the APIs finalized in their current state now, and then have those concerns be addressed through refinement later (like #204853).

  3. Locwyn42 commented on Mar 4, 2024

    @Locwyn42

    #203850
    Please, let us select specific GitHub accounts for each extension, many of us dream of having our paid Github Copilot from our personal Github account and the repository management for the work account.

  4. changed the title [-]Iteration Plan for March 2024 [DRAFT][/-] [+]Iteration Plan for March 2024[/+] on Mar 5, 2024
  5. oenu commented on Mar 5, 2024

    @oenu

    Heads up the

    🏃 Improvements to the Remote extensions, see [plan](https://github.com/microsoft/vscode-remote-releases/issues?q=is%3Aissue+label%3Aiteration-plan+milestone%3A%22March+2024%22) @roblourens @chrmarti @connor4312 @joyceerhl

    has been a broken link for a while
    replace with

    https://github.com/microsoft/vscode-remote-release/issues?q=is%3Aissue+label%3Aiteration-plan+milestone%3A%22March+2024%22
    

    ....soft/vscode-remote-release<S>/iss... => ....soft/vscode-remote-release/iss...

  6. sbatten commented on Mar 7, 2024

    @sbatten
    Member

    Hi John Murray (@gjsjohnmurray), I appreciate your feedback and also your many contributions to the project over the years. I can understand the frustration of waiting an indeterminate amount of time for a long-standing feature request for which you have personal interest. As you may know, our team members have responsibilities beyond the iteration plan items here and that this comes into play when creating the right balance for each team member's plan. That being said, I am aware of your requests as João Moreno (@joaomoreno) has brought them up to me and it is something that Andrea Mah (@andreamah) and I have on our radar and discussed. I ask for your understanding and please remain patient as we look for ways to make progress on those items.

  7. BartolomeSintes commented on Mar 13, 2024

    @BartolomeSintes

    "Iteration plan" issues are very useful to know about VSCode short term development. Perhaps comments could be closed to non-collaborators, but why unpin the issue?

  8. MasterInQuestion commented on Mar 18, 2024

    @MasterInQuestion

        Unsure it's situation:
        "workbench.action.compareEditor.swapSides" no-op on "workbench.files.action.compareWithSaved" diff
        https://github.com/microsoft/vscode/issues/204560#issuecomment-1975257379
        .
        But I doubt it merits another issue to needlessly clutter the issue list.

  9. starball5 commented on Apr 8, 2024

    @starball5

    Disappointment again that neither #59921 nor #73524 are listed, and that Andrea Mah (@andreamah)'s only item (#204853) involves polishing a recently-added feature (Quick Search, specifically its Previewing capability) that is still not available (polished or unpolished) to our userbase (pinging Brett Saviano (@isc-bsaviano)) because those two proposed APIs have remained unfinalized for more than 5 years now.

    John Murray (@gjsjohnmurray) You might be happy to see #209775

  10. locked and limited conversation to collaborators on Jun 10, 2024
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

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions