-
Notifications
You must be signed in to change notification settings - Fork 29.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Iteration Plan for May 2018 #49327
Comments
@WaiSiuKei Also, #17060 |
Just want to mention that the latest Windows update 1803 has issues with custom title bars. See my issue telegramdesktop/tdesktop#4649 for more information. |
any chance to get #10026 on board? |
@guledali the people working on the features will fill in the issue references eventually 😄 |
On this topic, any chance a "bleeding-edge" VS Code version could exist that makes use of the latest release of Electron (and possibly Node.js and Chromium)? Basically a rolling-release model which you've got dev, test, and stable. KDE Neon and Kali come to mind with this approach. |
Insiders version is there. |
yes but that doesn't address the model I'm proposing. Insiders is basically the dev and test combined (in a beta stage) with stable while the dev/test/stable is alpha/beta/prod. Different release mechanism. A third option would need to appear under the guise of Insiders similar to Fast-ring and Slow-ring for Windows Insider builds. |
Insiders is nightly builds. I don't see how we can get more alpha than that. |
Yes but that would be one of the changes. The nightly could be of the alpha such as Firefox does it, and weekly could be the beta and monthly be the stable (or however long it's needed to deem it "stable") The alpha would have auto-commits per change on dependencies (a commit to NodeJs or Electron for example would update over to here instead of manually pulling it down and pushing back up) (at least on a 12 hour increment to meet the nightly update schedule). The beta would have the tweaking optimizations that ensure that at least nothing breaks even if in a rough state while the stable would be polished out. A somewhat more Agile approach that what's currently done if I understand the release schedule correctly. |
@DarthSpock but that's not at all compliant to the work item planning right in front of you. What you are asking them for is a weekly release cycle, a weekly planning cycle... which would change things on so many ends i wouldn't be able to accurately predict the impact and i would assume neither can the more active contributors... As you can see simply through the existence of 0.X.1 Or 0.X.2 releases in the past, there already is a fast action plan in place allowing them to iterate small to hotfix something. We don't need a seperate release channel for that, especially if that potentially increases planning requirements a ton while simultaneously forcing contributors to edge down the integration process of their features to one week. The latter is the biggest nono i see in your proposal. |
I don't know where else to put this but would it be possible to close ticket on previous features that were half implemented? These 2 features have been pushed away for so long without any love
|
@ghiscoding thanks for the feedback we will keep it in mind for future iteration planning. For now I suggest to vote on individual feature requests. |
Closing - 1.24 has been shipped. |
This plan captures our work in May. This is a 5-week iteration. We will ship our May Update in early June.
In this iteration, we'll provide a preview of the grid layout support for the editor as well as an alternative UI for configuring settings. We'll also look into ways to provide outline information for open documents.
Endgame
The endgame details for this iteration are tracked in #50477.
Plan Items
Below is a summary of the top level plan items.
Legend of annotations:
Workbench
Editor
Terminal
Terminal
menu for better discoverability Add a top-levelTerminal
menu for better discoverability #49477 @TyriarLanguages
Language Server Protocol
JavaScript/TypeScript
Move to New File
refactoring 'Move to new file' refactoring for JavaScript and TypeScript #49866 @mjbvzCSS/HTML/JSON
Debug
nodemon
re-attach issue Nodemon restarts twice on file changes #48501 @roblourensExtension Contributions
tslint
running as a TypeScript server plugin Upgrade the extension to the latest TS support vscode-ts-tslint#7 @egammavetur
extension @octrefwebroot
andpathmapping
in the Chrome Debugger Support Dart debugging with Chrome-Debug #49472 @roblourensxterm.js
project new parser xtermjs/xterm.js#1399 Modularize the character atlas system, add a LRU-cache based dynamic character atlas xtermjs/xterm.js#1327 Support font ligatures xtermjs/xterm.js#958 @TyriarExtensions
API
Serviceability
Engineering
Documentation
Deferred Items
The text was updated successfully, but these errors were encountered: