Skip to content

Iteration Plan for January 2024 #201255

Description

@kieferrm

This plan captures our work in January. This is a 4-week iteration. We will ship in early February.

Endgame

  • January 23, 2024: Endgame begins
  • January 26, 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

Notebook Editor

Jupyter Notebooks

WebAssembly Support

Languages

Python

Language Server Protocol

TypeScript

Source Control

Testing

Debug

Debug Adapter Protocol

API

Extensions

Extension Contributions

Engineering

Electron


Deferred

Activity

  1. added this to the milestone on Dec 20, 2023
  2. changed the title [-]Iteration Plan for January 2024 [DRAFT][/-] [+]Iteration Plan for January 2024[/+] on Jan 3, 2024
  3. Cpt-Falcon commented on Jan 16, 2024

    @Cpt-Falcon

    Any word on whether copy paste is going to be fixed? You can't copy a variable during debugging without visual studio truncating saying "...". Quite a nuisance. Only way to get the contents of a larger variable is to write it out to a json file. Visual studio 2022 doesn't have this problem and limitation. I would understand if it truncated past 1000, but truncating it at like 20 is ridiculous. Maybe put a setting in the vs code settings that does not restrict on copying large variable values from the debugger

  4. jstm88 commented on Feb 1, 2024

    @jstm88

    How about addressing the fact that extensions are constantly able to spam the "Output" panel and there is no way to prevent it?

    I opened #203478 in an attempt to get the discussion in #105270 restarted, but all mentions of this problem keep getting incorrectly closed as "duplicates" because the original report from over 6 years ago was closed without fully understanding the issue.

    Not sure what users are supposed to do when a rogue mod starts closing valid issues and then not even looking at the discussion where users are calling for it to be reopened...

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

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions