Skip to content

Latest commit

 

History

History
197 lines (188 loc) · 11.6 KB

Endgame-Template.md

File metadata and controls

197 lines (188 loc) · 11.6 KB
  • Month/Day Code freeze for the endgame
  • Month/Day Endgame done
  • Month/Day Expected release date (this may change)
Monday
Tuesday
Wednesday
  • 🔖Testing
  • Remind team members to assign issues that they intend to fix to the current milestone
  • Fixing (self-assigned, milestone assigned)
  • 🔖Verification needed
  • Prepare for Smoke test: Make sure all smoke test issues are labelled smoke-test and fixed endgame champion
Thursday
  • Fixing (self-assigned, milestone assigned, NO discussion during standup)
    • Move issues to the next month that can be deferred
  • 🔖Verification needed
  • 🔖Verification
  • Prepare for Smoke test: Make sure all smoke test issues are labelled smoke-test and fixed endgame champion
Friday
  • Pause scheduled insider builds endgame champion
  • Satellite modules/npm packages ready, version updated, smoke tested
    • vscode @eamodio
    • yo generator @aeschli
    • vsce @joaomoreno
    • node debug @weinand
    • node debug2 @roblourens
    • js-debug @connor4312
    • node debugadapter node @weinand
    • custom data for html/css @aeschli
  • All issues 🔖verified
  • Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
  • Smoketest (⚠️ MUST run with --stable-build argument ⚠️ )
    • Windows - owner
    • macOS - owner
    • Linux - owner
    • Web (Chromium) - owner
  • All release notes updated
    • release notes are collected in a file named v<Major>_<Minor>.md in this repo directory
    • @aeschli
    • @alexdima
    • @alexr00
    • @bpasero
    • @chrmarti
    • @connor4312
    • @dbaeumer
    • @deepak1556
    • @eamodio
    • @egamma
    • @isidorn
    • @JacksonKearl
    • @joaomoreno
    • @jrieken
    • @kieferrm
    • @lszomoru
    • @meganrogge
    • @mjbvz
    • @rebornix
    • @rmacfarlane
    • @roblourens
    • @rzhao271
    • @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 champion
    • vscode-node-debug @weinand
    • vscode-node-debug2 @roblourens
    • 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 @weinand
    • localization @weeteckt
    • vscode-github-issues-prs @chrmarti
    • inno-updater @joaomoreno
  • Review pull requests acknowledgements with NOT MERGED - PLS REVIEW. endgame champion
  • 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 champion
  • Branch code to release/<x.y> endgame champion
  • Bump up the version in package.json on master - endgame champion
  • Announce master is open for business endgame champion
Friday/Monday
  • Polish release notes redmond
  • Fixing (only critical bugs - no string changes)
Monday - Wednesday
  • 🔖milestone issues
  • 🔖candidate issues
  • Polish release notes redmond
  • Cherry-pick hand-picked and reviewed changes to release/<x.y> endgame champion
  • Build Insider from release/<x.y> endgame champion
  • Manually release Insider endgame champion
  • Build stable for all platforms as new candidate issues come in endgame champion
  • Documentation updated
    • @aeschli
    • @alexdima
    • @alexr00
    • @bpasero
    • @chrmarti
    • @connor4312
    • @dbaeumer
    • @deepak1556
    • @eamodio
    • @egamma
    • @isidorn
    • @JacksonKearl
    • @joaomoreno
    • @jrieken
    • @kieferrm
    • @lszomoru
    • @meganrogge
    • @mjbvz
    • @rebornix
    • @rmacfarlane
    • @roblourens
    • @rzhao271
    • @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.

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

Wednesday/Thursday - Expected release day (this may change)
  • Build stable for all platforms endgame champion
  • Sanity check of installable bits
    • Windows 32 bit owner
      • signed installer 32-bit
      • signed user installer 32-bit
      • zip 32-bit
    • Windows 64 bit owner
      • signed installer 64-bit
      • signed user installer 64-bit
      • zip 64-bit
    • Windows ARM64 owner
      • signed installer ARM64
      • signed user installer ARM64
      • zip ARM64
    • macOS - owner
    • Linux
      • deb package 64-bit owner
      • rpm package 64-bit owner
      • archives owner
      • snap (sudo snap install --classic --dangerous <file>.snap) owner
    • Linux ARM64
      • deb package owner
      • rpm package owner
      • archives owner
    • Server (instructions) owner
      • Linux owner
      • macOS owner
      • Windows owner
  • Publish website @gregvanl
  • Publish Localization language pack @weeteckt
  • Publish to stable endgame champion
  • Create an official release endgame champion
    • Create a tag: git tag <x.y.z>
    • Push the tag: git push origin <x.y.z>
    • Create a GitHub release: Open the GitHub tags, and click far right ... > Create Release. Use the correct title and description from our release notes. Example
  • Publish @types/vscode endgame champion
  • Enable scheduled insider builds endgame champion
  • Twitter announcement @chrisdias