Skip to content

Iteration Plan for July 2025 #255701

Description

@kieferrm

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

Endgame

  • July 28, 2025: Endgame begins
  • August 1, 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

UX

Workbench

Getting started

Code Editor

Notebook Editor / Jupyter Notebooks

Source Control

Settings

Extensions

Languages

TypeScript and JavaScript

Python

Terminal

Tasks

API

Extension Contributions

GitHub Pull Requests

AI

MCP

Prompt and Instruction Files

  • None.

Chat

Terminal/task tools

NES / Completions

Integrations

Engineering

Electron

Documentation

Website


Deferred

Activity

  1. iwangbowen commented on Jul 14, 2025

    @iwangbowen

    Always looking forward to new updates

  2. changed the title [-]Iteration Plan for July 2025 [DRAFT][/-] [+]Iteration Plan for July 2025[/+] on Jul 17, 2025
  3. wadamczyk-insolutions commented on Jul 17, 2025

    @wadamczyk-insolutions

    Kai Maetzel (@kieferrm) Is there any chance of looking at #117862 in this or next iteration? Please 🥺 . This is a simple change that's been waiting for merging since February 2025 and is a known bug in VS Code for 4+ years, all checks have passed, from what I understand it only needs to be reviewed by 2 people from the core VS Code team, and the problem is very frustrating when working on large codebases with deep directory structures. This simple change would bring immense happiness to my small team, because now after every VS Code update we have to patch the internal CSS just to be able to work on our projects.

    I know that there were plans for the new UI of the quick widget, but... since it's been already 4 years and the change in the existing UI is only a few CSS lines...

    Thanks!

  4. teuxnkha619-design commented on Jul 18, 2025

    @teuxnkha619-design
  5. teuxnkha619-design commented on Jul 18, 2025

    @teuxnkha619-design
  6. volado821 commented on Jul 21, 2025

    @volado821

    #253268

    lopezkevin57668@gmail.com contáctenme a ese correo

  7. Frulfump commented on Jul 29, 2025

    @Frulfump

    Kai Maetzel (@kieferrm)
    Can't almost see the checked off check boxes due to contrast issues so checking what it looks like live

    • Checked
    • Not Checked

    (On Android GitHub mobile app in dark mode)
    Reported in GitHub discussion here with clear examples https://github.com/orgs/community/discussions/167961
    It looks like non-interactive checkboxes is greyed out with bad contrast and active ones are white/blue and very clear.

  8. locked and limited conversation to collaborators on Sep 24, 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