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

November/December Iteration Plan #15099

Closed
kieferrm opened this issue Nov 7, 2016 · 4 comments
Closed

November/December Iteration Plan #15099

kieferrm opened this issue Nov 7, 2016 · 4 comments
Assignees
Labels
iteration-plan VS Code - Upcoming iteration plan
Milestone

Comments

@kieferrm
Copy link
Member

kieferrm commented Nov 7, 2016

This plan captures what we work on during November and early December. This iteration will be 6 weeks long. This is unusually long for us. We are an internationally distributed team and everybody in the team wants to enjoy the forthcoming holiday season while we still continue working as a closely knit team. Thus, it's 6 weeks this time. We will ship mid December.

Not unusual and still noteworthy: We will do several explorations that might or might not result in concrete deliverables in this or later releases.

Endgame Schedule

  • December, 5th Code freeze for the endgame
  • December, 9th Endgame done
Monday - 5th December
  • Code freeze at 5pm PT
  • Ensure we have a green build on all platforms
  • All test items contain sufficiently comprehensive test descriptions by 6pm PT
Tuesday - 6th December
  • Test build starts at 7am CET / 10pm PT on Monday
  • Test plan ready by 8am CET / 11pm PT on Monday
  • Testing
Wednesday - 7th December
  • Testing
  • Remind team members to assign issues that they intend to fix to the November milestone
  • Fixing (self-assigned, milestone assigned)
  • Verification Since there are quite some old bugs to verify we verify by age, youngest first. The queries are:
Thursday - 8th December
  • Remind team members to start add Release Notes
  • Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • Verification
  • Add/update shrink-wrap files for built-in extensions if needed (see instructions) @ramya-rao-a
  • Update OSSREADME.json for built-in extensions based on differences to generated npm-shrinkwrap.json files if needed @ramya-rao-a
  • Run OSS tool after merging shrink-wrap findings @ramya-rao-a
    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
  • Check new OSS usage is entered into the OSS registry @ramya-rao-a
Friday - 9th December
Friday- 9th December
  • Branch code to `release/<x.y> @zurich
  • Announce master is open for business @zurich
Monday - 12th December
Tuesday - 13th December
Wednesday - 14th December

Plan Items

Our team uses a GitHub Project to track its work. GitHub does not support public Projects right now. Below is a summary of the top level plan items.

Legend for annotations:

Mark Description
🏃 work in progress
blocked task
💪 stretch goal for this iteration
🔵 more details required
🔴 missing issue reference

Themes

  • performance
  • discoverability
  • UI scalability
  • API improvements
  • accessibility testing

Feedback

Issues to address community feedback:

API Improvements for Extensions

Language support

Debt Items

Issues to reduce our engineering debt:

Extension Contributions

Support/contribute to extensions:

  • All - Ensure all extensions we contribute to are using the extension change log @kieferrm
  • 🏃 PHP - Continue exploration of improved PHP parser with symbol and location information PHP parser explorations #15818 @mousetraps
    • Discuss parser exploration with community
  • Go - Explore Go language server seeded by SourceGraph @ramya-rao-a
  • Azure - Explore Azure extension pack for the market place @chrisdias

Engineering

This section lists several engineering/development items that the team identified:

Feedback Channels

Explorations

We are continuously exploring options and ideas. Some might make it into future releases.

@kieferrm kieferrm added the iteration-plan-draft VS Code - Upcoming iteration plan (Draft) label Nov 7, 2016
@kieferrm kieferrm added this to the November 2016 milestone Nov 7, 2016
@rozzzly
Copy link

rozzzly commented Nov 7, 2016

I think everybody can agree

<< removed gif>> killed fun

This is a pretty exciting agenda.

Can wait to see how it unfolds!

@rebornix @alexandrudima If you're revisiting the diff viewer, could you look into a cool merge-mode feature like JetBrains has? Here's a video

The one thing I am sad to see missing is custom inline widgety-things ala #3220. I understand your initial investigation into the concept wasn't promising, but don't give up!!

OP mentions:

Describe our UX process for the team and the community

and a few other vague references to "contributable explorers.. but might it be wiser to address UI extensibility as a whole rather than a case by case basis? _This extensibility is the one thing that I believe vscode is lacking._ If this is November / December track... can January be overhaul of UI extensibility?? Custom sidebars, popovers, custom workspace css, etc. It's no small order, but that would bump up extensibility up a few orders of magnitude.

Anyway, that's my 2¢.

@eamodio
Copy link
Contributor

eamodio commented Nov 7, 2016

Sounds great!

Since the diff viewer is going to be looked at -- a feature I would love to have (and others on my team have echoed) would be small buttons (or something) to be able to quickly move change blocks from on side to the other. Of course these would only be available if one side of the diff was editable.

This is how Beyond Compare does it.
image

@darcome
Copy link

darcome commented Nov 8, 2016

I agree with PHP support! A very promising extension is https://marketplace.visualstudio.com/items?itemName=felixfbecker.php-intellisense

You could help me with his work!

@egamma
Copy link
Member

egamma commented Dec 15, 2016

Closing - November has been shipped

@egamma egamma closed this as completed Dec 15, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
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

6 participants