You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This plan captures our work in September. This is a 4-week iteration. We will ship our September Update in early October. As mentioned in July having many actively engaged users means high GitHub issue traffic, and we always have to walk the delicate balance between being responsive to issues and getting sufficient focus time to get things done. Now, it's this time of the year again, the time we tip the balance toward issue grooming.
We'll go through all of our issues in all our repositories, ensure all issues are labeled correctly and have the correct owners, close duplicates, fix bugs. This time, we'll also think about reducing the number of open feature requests. At the time of writing, we have more than 3000 open feature requests. For you and us it would be better if the set of open feature requests is more reflective of what has a chance to be considered within the next 12 - 24 months.
So, if all of a sudden you see a lot of GitHub notifications, don't get scared.
Endgame
September 24th, 2018: Code freeze for the endgame
September 28th, 2018: Endgame done
The endgame details for this iteration are tracked in #59271.
#5953 Please add this to the your plans if possible. Thanks! Would be nice to even hear something from a contributor on if there's any hope of getting File > Print added. Thanks again! Also, sorry if this isn't the place for this. I will not do this again, if I shouldn't. Sorry. Still learning Github.
This plan captures our work in September. This is a 4-week iteration. We will ship our September Update in early October. As mentioned in July having many actively engaged users means high GitHub issue traffic, and we always have to walk the delicate balance between being responsive to issues and getting sufficient focus time to get things done. Now, it's this time of the year again, the time we tip the balance toward issue grooming.
We'll go through all of our issues in all our repositories, ensure all issues are labeled correctly and have the correct owners, close duplicates, fix bugs. This time, we'll also think about reducing the number of open feature requests. At the time of writing, we have more than 3000 open feature requests. For you and us it would be better if the set of open feature requests is more reflective of what has a chance to be considered within the next 12 - 24 months.
So, if all of a sudden you see a lot of GitHub notifications, don't get scared.
Endgame
The endgame details for this iteration are tracked in #59271.
Plan Items
Below is a summary of the top level plan items.
Legend of annotations:
Accessibility
add
Github Issue Housekeeping
Workbench
Languages
TypeScript/JavaScript
Debug
Extension Contributions
xterm.js
Buffer performance improvements xtermjs/xterm.js#791 @Tyriarvscode-go
Support Go modules vscode-go#1532 @ramya-rao-aAPI
maxResults
indicator after a custom number of results Allow text search providers to show the maxResults indicator after a custom number of results #55790 @roblourensEngineering
master
@joaomorenospdlog
for output channels straight from the extension host Use spdlog for output channels straight from the extension host #57618 @sandy081Documentation
Deferred Items
None.
The text was updated successfully, but these errors were encountered: