Iteration Plan for October 2021

[kieferrm]

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

As you can see the plan is rather lean as this is our annual house-keeping iteration. You'll see a large number of GitHub issue notifications over the course of this iteration. If you want to track our progress, @lannonbr created this nice website a couple of years ago https://vscode-github-stats.netlify.com/

If you are interested in why we have issue house keeping iterations and in our general philosophy around issue management, then we have this write-up for you.

House-keeping is not the only focus this iteration. We'll also work closely with our partners at GitHub to get GitHub Codespaces in great shape.

Endgame

• October 26, 2021: Endgame
• October 29, 2021: 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

Housekeeping

• 🏃 Issue/PR Grooming - review, categorization, assignment vscode#134380 team

Accessibility

• Accessibility issues, see query @isidorn team
• 🏃 Debug Adapter Protocol website accessibility issues, see query @sana-ajani @gregvanl

Jupyter Notebooks

• Contributions to the vscode-jupyter extension vscode-jupyter#7874 @greazer team

Languages

Python

• Contributions to the python extension vscode-python#17683 @brettcannon team

API

• API finalization: query

---

Deferred Items

• All work that was in-flight end of September. We'll resume that work in early November.

[cyberfox1]

Please fix the multiple-window opening crap that has been raised in multiple issues but still keeps occurring.

[noahehall]

@shujaatak wtf are you talking about dude just install a new theme, e.g. dracula

and if you need the best vscode setup on the planet, check out my sync settings gist

[ElianCordoba]

@shujaatak What a disrespectful message to the people that are building something you are using for free. Instead of complaining why don't you provide some constructive feedback? Even better you can code it yourself.
Replacing that entitlement with humility and thankfulness will get you a long way, maybe even will get you a better looking and more usable code editor.

[ElianCordoba]

@shujaatak Ah nice edit there, the message it's almost reaching the minimum respectfulness level required to establish good communication. Let me help you a bit, here is how I would write your message:

Hi VS Code team!
I love the editor, but I've been having some usability issues around the space between the gutter and the editor's content/code. I've opened issue #135114 with more details.
It would be awesome if you could consider adding that issue to the next sprint. Let me know if I can help in any way.
Keep the good work coming!

[shujaatak]

Well, as I see where the things are going so I am going to delete my comment and apologize.
Thank you!

By the way, if you also like to resolve this issue #135114 then please give it thumbs up.
Peace!

[GHOSTS15]

Add " Explore simplifying enabling/disabling a group of extensions for a workspace vscode#40239 @lszomoru"

[GHOSTS15]

Add " Explore simplifying enabling/disabling a group of extensions for a workspace vscode#40239 @lszomoru"

P.s I hope the things you failed to implement (in September) you did not discard , if you discarded them it is ridiculous , shameful and makes -100% logical sense.