Skip to content

Iteration Plan for January 2025 #237297

Closed
Closed

Description

@kieferrm

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

Since mid-December, GitHub Copilot has been available for free for everyone. This allows us to treat AI support as an out-of-the-box experience in VS Code. Consequently, going forward, we'll cover our client-side work for Copilot in this plan, similarly to how we have been tracking our work on our Remote Extensions over the last years.

Endgame

  • Jan 27, 2025: Endgame begins
  • Jan 31, 2025: 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

Notebook Editor

Jupyter Notebooks

Settings

Languages

Python

TypeScript

  • None.

Authentication

Source Control

Testing

  • None.

Terminal

API

Extensions

Extension Contributions

Remote Extension Contributions

General

  • None.

SSH Extension

GitHub Copilot

Engineering

Electron

Documentation


Deferred

Activity

  1. iwangbowen commented on Jan 6, 2025

    @iwangbowen

    Couldn't wait for the next update

  2. changed the title [-]Iteration Plan for January 2025 [DRAFT][/-] [+]Iteration Plan for January 2025[/+] on Jan 6, 2025
  3. hickford commented on Jan 10, 2025

    @hickford
    Contributor

    Any time to look at bug fix #216085 ?

  4. Patrikoska1 commented on Jan 10, 2025

    @Patrikoska1
  5. commonism commented on Jan 13, 2025

    @commonism

    Hi,

    I'd like to discuss #869

    For me - the problem is …

    Having a ml project which includes the training/validation data on a remote server, the current vscode behavior is spidering all resources, installing inotify handlers, and if these fail due to the number, fstat all files.

    You end up with a vscode node.js services breaking your ml storage backend by running fstat for 200k files at the speed possible.

    This is bad defaults and currently users are even unable to change these defaults.

    Depending on the storage backend, tracking down users/projects causing these metadatalookups is manual task and very time consuming.

  6. fisforfaheem commented on Jan 13, 2025

    @fisforfaheem

    Anything related to UI and UX? because the audio cue are not easily enabled or disabled, also the UI need to be much like windows 11 mica style now

  7. ARCHE7YPE commented on Jan 14, 2025

    @ARCHE7YPE

    Any time to look at bug fix #216085 ?

    "Community PR Approvals In progress — Not enough approvals" - tough test.

  8. YangtzeCoder commented on Jan 20, 2025

    @YangtzeCoder

    Any plan to #213489 ?

  9. eshimischi commented on Jan 22, 2025

    @eshimischi

    Any plans about moving to Tauri someday?

  10. Neodevils commented on Jan 24, 2025

    @Neodevils

    After a while I coded, my whole syntax highlight & system gets worse. I don’t know why.

  11. Adiwibowo9 commented on Jan 27, 2025

    @Adiwibowo9

    good luck

  12. AlexiaChen commented on Feb 4, 2025

    @AlexiaChen

    Seems copilot features are far behind Cursor........

  13. locked and limited conversation to collaborators on Mar 23, 2025
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

    ⌂ 换网址