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

June Iteration Plan #7253

Closed
egamma opened this issue Jun 6, 2016 · 5 comments
Closed

June Iteration Plan #7253

egamma opened this issue Jun 6, 2016 · 5 comments
Assignees
Labels
iteration-plan VS Code - Upcoming iteration plan
Milestone

Comments

@egamma
Copy link
Member

egamma commented Jun 6, 2016

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

We arrived at the following themes for June:

  • Remove the most requested adoption blockers.
  • Make the repository with the Monaco/standalone editor available.
  • Improve the getting started experience

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

For more information about our development process please refer to the development process page.

Schedule

  • June 27 Code freeze for the endgame June
  • June 29 Endgame done

End game dates (we end an iteration with an endgame)

Monday, Jun 27
  • Code freeze at end of day
Tuesday, Jun 28
  • Test plan input done at 8am Zurich time
  • Test plan ready
  • Test build done
  • Testing
Wednesday, Jun 29
  • Testing
  • Fixing
Thursday, Jun 30
  • Fixing
  • Run OSS tool
  • Verification
  • Update release notes
Friday, Jul 1
Monday, Jul 4
Tuesday, Jul 5
  • Polish release notes (Redmond)
  • Inbox review June Issue Review #8753
  • Publish Insider with hand-picked and reviewed candidate fixes
Thursday/Friday, Jul 7/8
  • Publish to stable
  • Enable scheduled insider builds

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:

Feedback

Issues to address feedback from the community:

Engineering

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

Explorations

Deferred

Bugs

Bugs assigned to the current milestone:

@glen-84
Copy link

glen-84 commented Jun 11, 2016

We arrived at the following themes for May:

Should be June. =)

TypeScript/JavaScript - Explore project level errors/warnings

Is this just "give tslint etc. the folder name instead of the file name", as opposed to VS Code actually keeping track of errors/warnings during an "indexing" process (where each file is processed separately)?

@egamma
Copy link
Member Author

egamma commented Jun 11, 2016

@glen-84 thanks for catching the typo.

Is this just "give tslint etc. the folder name instead of the file name", as opposed to VS Code actually keeping track of errors/warnings during an "indexing" process (where each file is processed separately)?

This is an investigation to add scalable project level errors to the typescript language service and tsServer. This is independent of tslint.

@niieani
Copy link

niieani commented Jul 3, 2016

Fantastic job guys. Honestly, you're developing faster than a lightning! Thanks a lot for making the best IDE out there.

🏆 🎆 💃

@fallenleavesguy
Copy link

thanks. good job

@egamma
Copy link
Member Author

egamma commented Jul 8, 2016

Shipped 1.3 closing

@egamma egamma closed this as completed Jul 8, 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

4 participants