Skip to content
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

Closed
36 of 46 tasks
kieferrm opened this issue May 7, 2018 · 15 comments
Closed
36 of 46 tasks

Iteration Plan for May 2018 #49327

kieferrm opened this issue May 7, 2018 · 15 comments
Assignees
Labels
iteration-plan VS Code - Upcoming iteration plan
Milestone

Comments

@kieferrm
Copy link
Member

kieferrm commented May 7, 2018

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

  • May 28th, 2018: Code freeze for the endgame
  • June 1st, 2018: Endgame done

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:

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

Workbench

Editor

Terminal

Languages

Language Server Protocol

JavaScript/TypeScript

CSS/HTML/JSON

Debug

Extension Contributions

Extensions

API

Serviceability

Engineering

Documentation


Deferred Items

@kieferrm kieferrm added the iteration-plan-draft VS Code - Upcoming iteration plan (Draft) label May 7, 2018
@kieferrm kieferrm added this to the May 2018 milestone May 7, 2018
@WaiSiuKei
Copy link

Investigate custom title bar and menus for improved accessibility on Windows @sbatten

I think it is related to #29024

@kieferrm kieferrm changed the title Iteration plan for May 2018 - DRAFT Iteration plan for May 2018 May 7, 2018
@kieferrm kieferrm added iteration-plan VS Code - Upcoming iteration plan and removed iteration-plan-draft VS Code - Upcoming iteration plan (Draft) labels May 7, 2018
@kieferrm kieferrm changed the title Iteration plan for May 2018 Iteration Plan for May 2018 May 7, 2018
@Kroc
Copy link

Kroc commented May 8, 2018

@WaiSiuKei Also, #17060

@levrik
Copy link

levrik commented May 9, 2018

🔴 Investigate custom title bar and menus for improved accessibility on Windows @sbatten

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.
Would also interesting if you guys could find out more about this issue internally at MS. It seems that every Win32 app with a custom titlebar is affected.

@ivanvoznyakovsky
Copy link

ivanvoznyakovsky commented May 10, 2018

any chance to get #10026 on board?

@guledali
Copy link

@kieferrm

Investigate custom title bar and menus for improved accessibility on Windows @sbatten

Why does it say missing issue reference the are numerous issues out there mention this. I can just list a few of them.
#39972
#32257
#29997
#17060

@Tyriar
Copy link
Member

Tyriar commented May 11, 2018

@guledali the people working on the features will fill in the issue references eventually 😄

@WSLUser
Copy link

WSLUser commented May 22, 2018

Deferred Items
Electron 2.0 update

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.

@gulshan
Copy link

gulshan commented May 22, 2018

Insiders version is there.

@WSLUser
Copy link

WSLUser commented May 22, 2018

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.

@sylveon
Copy link
Contributor

sylveon commented May 22, 2018

Insiders is nightly builds. I don't see how we can get more alpha than that.

@WSLUser
Copy link

WSLUser commented May 22, 2018

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.

@MeikTranel
Copy link

MeikTranel commented May 27, 2018

@DarthSpock but that's not at all compliant to the work item planning right in front of you.
They iterate Monthly with a focus on stabilizing at the end of each month aka "The Endgame", where they prepare the develop to be merged into master (branch names don't matter; insider / release, alpha / release all the same).

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.
When a contributor has to be able to guarantee that his/her feature is stably integrated within one week i really doubt there'd be any community contributors left who'd do large features.
Just look at some of the issues in this integration plan...

@ghiscoding
Copy link

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

@egamma
Copy link
Member

egamma commented Jun 7, 2018

@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.

@egamma
Copy link
Member

egamma commented Jun 7, 2018

Closing - 1.24 has been shipped.

@egamma egamma closed this as completed Jun 7, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jul 22, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
iteration-plan VS Code - Upcoming iteration plan
Projects
None yet
Development

No branches or pull requests