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

July Iteration Plan #8760

Closed
egamma opened this Issue Jul 5, 2016 · 5 comments

Comments

Projects
None yet
3 participants
@egamma
Member

egamma commented Jul 5, 2016

This plan captures what we work on during July and will ship early August.

Notice there will be a delay in 1.4 with regard to the translations and 1.4 will not be fully translated. We are planning for 1.5 to be fully translated release again.

June was a feature rich release and July is a heavy vacation month for the team. We have therefore decided that in July we will slow down feature work in favor of reducing our bug backlog and removing debt. Given this, we have the following themes for July:

  • Bug/Issue management: review, cleanse, fix
  • Reduce debt items
  • Engage and support popular extensions. We want to make sure that popular extensions are as good as possible so we will spend time supporting these extensions with feedback and Pull Requests.
  • React to feedback from the June release

The July Test Plan items are created as issues get closed.

Schedule

  • July 25 Code freeze for the endgame
  • July 29 endgame done

We end an iteration with an endgame. The endgame is driven by Redmond.

Monday, Jul 25
  • 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, Jul 26
  • Test build starts at 7am CET / 10pm PT on Monday
  • Test plan ready by 8am CET / 11pm PT on Monday
  • Testing
Wednesday, Jul 27
  • Testing
  • Fixing (self-assigned, milestone assigned, and labeled as candidate)
  • Verification
Thursday, Jul 28
  • Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting)
  • Verification
  • Update release notes
    • release notes are collected in a file named Month_Year.md in this repo directory
  • Add/update shrink-wrap files for built-in extensions if needed (see instructions) @Tyriar
  • Update OSSREADME.json for built-in extensions based on differences to generated npm-shrinkwrap.json files if needed @Tyriar
  • Run OSS tool after merging shrink-wrap findings @Tyriar
    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
  • Check new OSS usage is entered into the OSS registry @Tyriar
Friday, Jul 29
  • Pause scheduled insider builds @zurich
  • Satellite modules/npm packages ready, version updated, smoke tested
  • Translation input - @isdorn
  • All issues verified
  • Fixing (only critical bugs - no string changes)
  • Smoketest
  • All release notes updated
    • release notes are collected in a file named Month_Year.md in this repo directory
  • Acknowledge pull requests in release notes @Tyriar
  • Mention notable fixes in the release notes
Monday, Aug 1
  • National Day in Zurich
  • Trigger new insider build and publish it manually (was delayed due to build server issue) @Tyriar
  • Polish release notes @redmond
Tuesday, Aug 2
  • Resubmit translation input @zurich
  • Branch code with release number @zurich
  • Announce master is open for business @zurich
  • Publish Insider with hand-picked and reviewed candidate fixes @jrieken
Thursday/Friday, Aug 4/5

Plan Items

Mark Description
🏃 work in progress
task is blocked
💪 stretch goal for this iteration

Debt Items

This section lists items to reduce our engineering debt:

  • Reduce our high contrast theme CSS hacks and inline SVGs during build #8516 @bpasero
    • Test #9692
    • Release notes
  • Allow to have scoped instantiation service per editor slot #8579 @bpasero
    • Test #9693
    • Release notes
  • Menu/title bar contribution consistency for the editor context menu @jrieken
    • Test #9694
    • Release notes
  • 🏃 Improve integrated terminal i18n support #8936 @Tyriar
    • Test #9695
    • Release notes
  • Snippet improvements #9072, #9122, #6320, #9286 @jrieken, @aeschli
    • Provide a setting to define the snippet sort order
      • Test #9696
      • Release notes
    • Provide a separate 'Insert snippet' command that allows the user to pick a snippet
      • Test #9697
      • Release notes
    • Support tab completion for snippets #9579 @jrieken
      • Test #9698
      • Release notes

Feedback

Issues to address community feedback:

Engineering

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

Explorations

  • 🏃 Node debugging - investigate into supporting/switching to the Chrome Debugger Protocol that comes with node 7.0 @weinand
    • Release notes
  • 🏃 Review/investigate current error telemetry @ramya-rao-a

Deferred

  • Debug: Add modules view @isidorn@weinand
  • Simplify configuration support and enable to programmatically modify configurations #8937 @bpasero
  • Add the Language Extension Checklist to our docs @kieferrm

Bugs

Bugs assigned to the current milestone:

@egamma egamma added this to the July 2016 milestone Jul 5, 2016

@egamma egamma self-assigned this Jul 5, 2016

@johnfn

This comment has been minimized.

Show comment
Hide comment
@johnfn

johnfn Jul 9, 2016

Contributor

Maybe this isn't the best place to put this, but I'm a Vim extension developer and I noticed you guys wanted to know the API gaps. I made an issue for each gap I'm aware of: #2771, #8096, #1431, #8094, #8093, #7177.

#2771 is the highest priority because it can't be worked around.

#8096 is also really important because although it can be worked around, I'm scared of breaking user's history.

The rest would be very nice to have.

Contributor

johnfn commented Jul 9, 2016

Maybe this isn't the best place to put this, but I'm a Vim extension developer and I noticed you guys wanted to know the API gaps. I made an issue for each gap I'm aware of: #2771, #8096, #1431, #8094, #8093, #7177.

#2771 is the highest priority because it can't be worked around.

#8096 is also really important because although it can be worked around, I'm scared of breaking user's history.

The rest would be very nice to have.

@egamma egamma referenced this issue Jul 9, 2016

Closed

VIM API Gaps #8997

4 of 4 tasks complete
@egamma

This comment has been minimized.

Show comment
Hide comment
@egamma

egamma Jul 9, 2016

Member

@johnfn thanks, extracted into #8997

Member

egamma commented Jul 9, 2016

@johnfn thanks, extracted into #8997

@egamma

This comment has been minimized.

Show comment
Hide comment
@egamma

egamma Aug 8, 2016

Member

Closing - 1.4 has been shipped.

Member

egamma commented Aug 8, 2016

Closing - 1.4 has been shipped.

@egamma egamma closed this Aug 8, 2016

@niieani

This comment has been minimized.

Show comment
Hide comment
@niieani

niieani Aug 9, 2016

What came out of this exploration?

Node debugging - investigate into supporting/switching to the Chrome Debugger Protocol that comes with node 7.0 @weinand

Nothing was mentioned in the release notes :(

niieani commented Aug 9, 2016

What came out of this exploration?

Node debugging - investigate into supporting/switching to the Chrome Debugger Protocol that comes with node 7.0 @weinand

Nothing was mentioned in the release notes :(

@egamma

This comment has been minimized.

Show comment
Hide comment
@egamma

egamma Aug 9, 2016

Member

The first step was a gap analysis between the V8 node debugger adapter and the chrome debugger adapter. This is continued in August and the August plan has a link to the gap analysis.

Member

egamma commented Aug 9, 2016

The first step was a gap analysis between the V8 node debugger adapter and the chrome debugger adapter. This is continued in August and the August plan has a link to the gap analysis.

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