January 2020 Endgame

[sandy081]

• January 27 Code freeze for the endgame
• January 31 Endgame done
• February 5 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 endgame master
• Code freeze at 5pm PT
• Ensure we have a green build on all platforms at 5pm PT
• Create test plan items following the template here by 6pm PT
• Add verification-needed label to features needed testing and are not tested by TPIs.
• 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
  • Assigned to you
• 🔖All closed feature-requests either have a verification-needed or on-testplan label
• 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 needed

Thursday

• Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
• 🔖Verification needed
• 🔖Verification

Friday

• Pause scheduled insider builds endgame master
• Satellite modules/npm packages ready, version updated, smoke tested
  • vscode @bpasero
  • yo generator @aeschli
  • vsce @joaomoreno
  • debug adapter protocol @weinand
  • node debug @weinand
  • node debug2 @roblourens
  • node debugadapter node @weinand
• All issues 🔖verified
• Fixing (only critical bugs - no string changes)
• Smoketest (⚠️ MUST run with --stable-build argument ⚠️ ) - Run manually
  • Windows @rebornix
  • OS X @connor4312
  • Linux @JacksonKearl
  • Web (manual until Web Smoke Test: Run against produced build #80308 is done) - @sandy081
• All release notes updated
  • release notes are collected in a file named vMajor_Minor.md in this repo directory
  • @aeschli
  • @alexdima
  • @alexr00
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @mjbvz
  • @octref
  • @rebornix
  • @RMacfarlane
  • @roblourens
  • @sandy081
  • @sbatten
  • @Tyriar
  • @weinand
• Acknowledge pull requests in release notes. We acknowledge PRs from outside the team. Use the thankyou tool to generate the initial contents of the section. owner
  • vscode endgame master
  • vscode-node-debug @weinand
  • vscode-node-debug2 @roblourens
  • debug-adapter-protocol @weinand
  • vscode-debugadapter-node @weinand
  • vscode-js-debug @connor4312
  • vscode-languageserver-node @dbaeumer
  • language-server-protocol @dbaeumer
  • vscode-textmate @alexdima
  • vscode-loader @alexdima
  • vscode-generator-code @aeschli
  • vscode-vsce @joaomoreno
  • vscode-docs @gregvanl
  • vscode-css-languageservice @aeschli
  • vscode-json-languageservice @aeschli
  • vscode-html-languageservice @aeschli
  • jsonc-parser @aeschli
  • vscode-eslint @dbaeumer
  • vscode-jshint @RMacfarlane
  • vscode-recipes @chrisdias
  • localization @weeteckt
  • vscode-github-issues-prs @chrmarti
  • inno-updater @joaomoreno
• Review pull requests acknowledgements with NOT MERGED - PLS REVIEW. endgame master
• Acknowledge issue trackers from the community @chrmarti
• Add notable fixes to the release notes all
• 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 endgame master

Friday/Monday

• Branch code to `release/<x.y> 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

• 🔖milestone issues
• 🔖candidate issues
• Polish release notes redmond
• Cherry-pick hand-picked and reviewed changes to release/<x.y> endgame master
• Build Insider from release/<x.y> endgame master
• Manually release Insider endgame master
• Build stable for all platforms as new candidate issues come in endgame master
• Documentation updated
  • @aeschli
  • @alexdima
  • @alexr00
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @mjbvz
  • @octref
  • @rebornix
  • @RMacfarlane
  • @roblourens
  • @sandy081
  • @sbatten
  • @Tyriar
  • @weinand
• Run scripts/test-documentation.sh|bat and add file or fix issues if there are new colors that are not documented - @aeschli

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

Wednesday/Thursday

• Build stable for all platforms endgame master
• Sanity check of installable bits
  • Windows 32 bit @bpasero
    • signed installer 32-bit
    • signed user installer 32-bit
    • zip 32-bit
  • Windows 64 bit @dbaeumer
    • signed installer 64-bit
    • signed user installer 64-bit
    • zip 64-bit
  • OS X - @weinand
  • Linux
    • deb package 64-bit @jooamoreno
    • rpm package 64-bit @chrmarti
    • archives @jooamoreno
    • snap @jooamoreno
  • Server (instructions) @sandy081
• Publish website @gregvanl
• Publish Localization language pack @weeteckt
• Publish to stable endgame master
• Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) endgame master
• Publish @types/vscode endgame master
• Enable scheduled insider builds endgame master
• Twitter announcement @chrisdias

[gudvinr]

release notes are collected in a file named Month_Year.md

I think you kind of need to update your templates. It's named like vNext_Version.md for a while.

[Calebyang93]

Hi @sandy081, please add me in. I am interested to contribute.

[Tyriar]

@Calebyang93 unfortunately our endgame process isn't really set up for those outside the core team to contribute.

[Calebyang93]

@Calebyang93 unfortunately our endgame process isn't really set up for those outside the core team to contribute.

Thats fine! Thanks for clarifying! @Tyriar

[Techman]

The OSS tool link appears to be not found. Is this intentional?

[dhuber666]

Hi,

I can't wait for the settings sync in new version. Since 2 hours the checkbox "Manually Release Insider" is checked. Does that mean a new update arrives soon in my VSC Insider with settings sync?

Can't wait. You guys are the best, keep on with this awesome work you do!
Greets from Austria

[sandy081]

I can see your excitement but sad to say that Settings Sync is not yet available in insiders. We are working towards providing it soon - #90129

[GustavoASC]

Congrats for making this great editor!!!