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.

Sign up for GitHub

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

December/January 2019 Endgame #67225

Closed
dbaeumer opened this issue Jan 28, 2019 · 3 comments
Closed

December/January 2019 Endgame #67225

dbaeumer opened this issue Jan 28, 2019 · 3 comments
Assignees
@roblourens @dbaeumer
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
December/January ...

Comments

@dbaeumer
Copy link
Member

dbaeumer commented Jan 28, 2019 •
edited by Tyriar
Loading

Schedule Template

  • End game master: @dbaeumer / Zurich
  • End game body: @roblourens / Redmond
  • 01/28 Code freeze for the endgame
  • 02/01 Endgame done
  • 02/06 Expected release date (this may change)

Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame.

Monday
  • Run OSS tool @dbaeumer
    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
  • Code freeze at 5pm PT
  • Ensure we have a green build on all platforms at 5pm PT
  • All test items contain sufficiently comprehensive test descriptions by 6pm PT
  • Update your availability for testing here - https://vscode-tools.azurewebsites.net/
Tuesday
  • Test plan items assigned (using https://vscode-tools.azurewebsites.net/)
    • Run the tool multiple times to balance load if test items come in later and assignments are already made
  • All closed feature-requests either have a verification-needed or on-testplan tag
  • Test build starts at 7am CET
  • Test plan ready by 8am CET
  • Testing
  • Verification needed
Wednesday
  • Testing
  • Remind team members to assign issues that they intend to fix to the current milestone
  • Fixing (self-assigned, milestone assigned)
  • Verification
Thursday
  • Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • Verification
  • Check new OSS usage is entered into the OSS registry owner
Friday
Friday/Monday
  • Branch code to `release/1.31 endgame master
  • Bump up the version in package.json - endgame master
  • Announce master is open for business endgame master
  • Polish release notes redmond
Monday - Wednesday

Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame.

Wednesday/Thursday

Recovery Build

We release a recovery build with a handful of critical fixes and translation updates a few days after a release. The candidate fixes are reviewed by the development team and are assigned to the recovery milestone. We want to be restrictive about the included candidates. The mindset is "we will lose users if we do not include the fix". Here are some examples:

  • data loss
  • a regression that users complain loudly about in issues or twitter
  • a significant performance regressions
  • an issue that impacts many users as indicated by telemetry data
  • an embarrassing UI glitch
  • critical security fixes
  • an issue that impacts extensions or is an API regression

Check list

  • Create a milestone <Month> Recovery <year> owner
  • Bump the version number owner
  • Assign candidate issues to the recovery milestone team
  • Review the candidate issues, and if they pass the review assign them to the recovery milestone team
  • All candidate fixes are peer reviewed and pushed to master and then cherry-picked into the release branch team
  • Initiate insiders build from master
  • Issues are tested in the insiders team
  • Build stable for all platforms from release branch owner
  • Make rpm signing request @Tyriar
  • Issues are verified on stable build and the verified label is added owner
  • Check https://github.com/Microsoft/vscode/compare/release/<x.y> to ensure no other commits have been made in the release branch owner
  • Update the release notes and include a link to a query for the fixed issues @gregvanl
  • Smoketest stable bits
  • Sanity check installable stable bits that have not been smoke tested
    • Windows
      • signed installer 32-bit owner
      • signed installer 64-bit @Tyriar
      • zip 32-bit owner
      • zip 64-bit owner
    • OS X - owner
    • Linux
      • deb package 32-bit owner
      • deb package 64-bit owner
      • rpm package 64-bit owner
      • rpm package 32-bit owner
      • archives owner
  • Publish website @gregvanl
  • Publish stable build owner
  • Publish rpm to repository manually @Tyriar
  • Add a git tag to HEAD of release/1.31 in format 1.31.x
@vscodebot vscodebot bot added the install-update VS Code installation and upgrade system issues label Jan 28, 2019
@dbaeumer dbaeumer added endgame-plan VS Code - Next release plan for endgame and removed install-update VS Code installation and upgrade system issues labels Jan 28, 2019
@dbaeumer dbaeumer added this to the December/January 2019 milestone Jan 28, 2019
@kieferrm kieferrm mentioned this issue Jan 28, 2019
Closed
42 tasks
@KexyBiscuit KexyBiscuit mentioned this issue Feb 5, 2019
Closed
@shawndon
Copy link

shawndon commented Feb 6, 2019

Signing off on localization for February 2019 release (v1.31 Loc)

@Tyriar
Copy link
Member

Tyriar commented Feb 13, 2019

rpm published

@Tyriar Tyriar closed this as completed Feb 13, 2019
@mysticatea
Copy link

Hi. "Find in selection" button looks still broken: #68190

@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@roblourens roblourens

@dbaeumer dbaeumer

Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Milestone
December/January 2019
Development

No branches or pull requests
5 participants
@roblourens @dbaeumer @mysticatea @Tyriar @shawndon