Skip to content

/ vscode

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

Jump to bottom

October Iteration Plan #13342

Closed
egamma opened this issue Oct 7, 2016 · 6 comments
Closed

October Iteration Plan #13342

egamma opened this issue Oct 7, 2016 · 6 comments
Assignees
@egamma @kieferrm
Labels
iteration-plan
Milestone
October 2016

Comments

@egamma
Copy link
Member

@egamma egamma commented Oct 7, 2016 •
edited

This plan captures what we work on during October. We will ship early November.

Endgame Schedule

  • October, 24th Code freeze for the endgame
  • October, 30th Endgame done
Verification
Monday
  • 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
  • Test build starts at 7am CET / 10pm PT on Monday
  • Test plan ready by 8am CET / 11pm PT on Monday
  • Testing
Wednesday
  • Testing
  • Remind team members to assign issues that they intend to fix to the October milestone
  • Fixing (self-assigned, milestone assigned)
  • Verification (queries above)
Thursday
  • Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • Verification (queries above)
  • Add/update shrink-wrap files for built-in extensions if needed (see instructions)
  • Update OSSREADME.json for built-in extensions based on differences to generated npm-shrinkwrap.json files if @basero
  • Run OSS tool after merging shrink-wrap findings @bpasero
    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
  • Check new OSS usage is entered into the OSS registry @bpasero
Friday
Friday/Monday
  • When done fixing/verifying and there are changes since last build at the end of day PT
    • Trigger new insider build and publish it manually @bpasero
  • Pause scheduled insider builds @bpasero
  • Branch code to `release/<x.y> @bpasero
  • Announce master is open for business @bpasero
  • Polish release notes @gregvanl
Wednesday
Thursday/Monday

Plan Items

We are now using the new Project support to track the work planned for October.

The columns in the project mean:

  • Backlog - the backlog for the iteration
  • Planned to Start Current week - the work planned to start in the current week of the iteration
  • In Progress - the item is actively being worked on
  • Done - the work item is done and there is a corresponding test plan item.
@egamma egamma added this to the October 2016 milestone Oct 7, 2016
@egamma egamma changed the title October Iteration Plan (work in progress) October Iteration Plan Oct 10, 2016
@mi-hol
Copy link

@mi-hol mi-hol commented Oct 19, 2016 •
edited

Currently the github 'projects' page shows 'no due date'.
Community member are hence a bit in the dark about planned time lines and few will find this plan as its 'flagged' as issue. For another project I saw this type of information made visible via 'milestones' https://github.com/serverless/serverless/milestone/15
Hence I wonder if the dates published above would fit better on a 'milestones' page?
@egamma
Copy link
Member Author

@egamma egamma commented Oct 20, 2016

@mi-hol thanks for your feedback, the example link you provide below is not accessible to me.

Here is how I think about it:

  • we still use milestones on issues for when we plan to deliver an item. Milestones have a due date (it was an oversight to not assign a milestone date for October).
  • we use 'Projects' to track the progress on these issues we plan for October, i.e., Planned this week, in progress, done, deferred).
  • we use Cards in projects for for things that are under discussion and haven't hardened yet as issues.

Bottom line if you are not interested in the progress on an Issue as an external user, then you can just looks at the milestone of the issue and you can also look at the milestones page. However, the milestone page get difficult to digest when it has over 100 items. See the October Milestone as an example.
@mi-hol
Copy link

@mi-hol mi-hol commented Oct 24, 2016

@egamma thanks for your fast response. I've verified the supplied link and it doesn't work when clicked inside the issue for me either but copied into a browser it does. Weird that the link inside a GitHub issue doesn't work (maybe a GitHub bug). URL: https://github.com/serverless/serverless/milestone/15

  • Assigning a due date was addressing my comment (note: 'November 2016' milestone lacks it again)
@isidorn isidorn mentioned this issue Oct 25, 2016
Closed
@egamma
Copy link
Member Author

@egamma egamma commented Nov 7, 2016

Closing 1.7 has shipped
@egamma egamma closed this Nov 7, 2016
@mrmlnc
Copy link
Contributor

@mrmlnc mrmlnc commented Nov 7, 2016

Hello, @egamma,

Small clarification: VS Code team has plans to publish recovery release? Because now we have broken support JavaScript React (#14962) and Less/SCSS comments (#15013).
@egamma
Copy link
Member Author

@egamma egamma commented Nov 7, 2016

@mrmlnc thanks for pointing this out, added these issues as candidates to the October recovery build.
@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.
Assignees

@egamma egamma

@kieferrm kieferrm

Labels
iteration-plan
Projects
None yet
Milestone
  October 2016
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
@egamma @kieferrm @mrmlnc @mi-hol
You can’t perform that action at this time.