Vscode: February Endgame

Created on 26 Feb 2018  路  5Comments  路  Source: microsoft/vscode

Endgame Schedule

  • Feburary 26, Code freeze for the endgame
  • March 2, Endgame done

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

Monday

  • [x] Code freeze at 5pm PT
  • [x] Ensure we have a green build on all platforms at 5pm PT
  • [x] All test items are created (with "complexity" but not necessarily with full description) by 5pm PT
  • [x] All test items contain comprehensive test descriptions by 10pm PT
  • Testers who cannot participate in testing check-off from list below:

    • [x] @aeschli

    • [x] @alexandrudima

    • [x] @auchenberg

    • [x] @bpasero

    • [x] @chrisdias

    • [x] @chrmarti

    • [x] @dbaeumer

    • [x] @egamma

    • [x] @isidorn

    • [x] @joaomoreno

    • [x] @jrieken

    • [x] @kieferrm

    • [x] @mjbvz

    • [x] @octref

    • [x] @ramya-rao-a

    • [x] @rebornix

    • [x] @rmacfarlane

    • @roblourens

    • [x] @sandy081

    • [x] @seanmcbreen

    • [x] @tyriar

    • [x] @weinand

Tuesday

  • [x] [Test plan items](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+label%3Atestplan-item+milestone%3A%22February+2018%22) assigned
  • [x] [All closed feature-requests without either verification-needed or on-testplan tag](https://github.com/Microsoft/vscode/issues?utf8=%E2%9C%93&q=label%3Afeature-request+-label%3Aon-testplan+-label%3Averification-needed+-label%3A*duplicate+is%3Aclosed+milestone%3A%22February+2018%22)
  • [x] Testing
  • [x] [Verification needed](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+-label%3Averified+label%3Averification-needed+is%3Aclosed)

Wednesday

  • [x] Remind team members to assign issues that they intend to fix to the February milestone
  • [x] Testing
  • [x] [Fixing](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Abug+milestone%3A%22February+2018%22) (self-assigned, milestone assigned)
  • [x] [Verification needed](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+-label%3Averified+is%3Aclosed+label%3Averification-needed)
  • [x] [Verification](https://github.com/Microsoft/vscode/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+-label%3Averified+-label%3Aduplicate+-label%3A*duplicate+-label%3Ainvalid+-label%3Aerror-telemetry+-label%3Aas-designed+milestone%3A%22February+2018%22+is%3Aclosed+)

Thursday

  • [x] [Fixing last issues](https://github.com/Microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Abug+milestone%3A%22February+2018%22)
  • [x] [Verification needed](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+-label%3Averified+is%3Aclosed+label%3Averification-needed)
  • [x] [Verification](https://github.com/Microsoft/vscode/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+-label%3Averified+-label%3Aduplicate+-label%3A*duplicate+-label%3Ainvalid+-label%3Aerror-telemetry+-label%3Aas-designed+milestone%3A%22February+2018%22+is%3Aclosed+)
  • [x] Run OSS tool endgame master

    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore

    • do not forget to update the distro attribute in the package.json with the commit ID of the distro repo.

    • Create list for team members to enter new OSS usage into the OSS registry endgame master

Friday

  • Register new components in OSS registry
  • Satellite modules/npm packages ready, version updated, smoke tested

    • [x] vscode @bpasero

    • [x] yo generator @aeschli

    • [x] vsce @joaomoreno

    • [x] node-debugadapter-node @weinand

    • [x] node-debug @weinand

    • [x] node-debug2 @weinand

  • [x] Check translations (check i18n folder git history for latest translations, then build locally and see the amount of untranslated strings) @dbaeumer
  • [x] [Verification needed](https://github.com/Microsoft/vscode/issues?q=is%3Aissue+-label%3Averified+is%3Aclosed+label%3Averification-needed)
  • [x] Fixing (only critical bugs - no string changes)
  • Smoketest

    • [x] Windows - @dbaeumer

    • [x] OS X - @weinand

    • [x] Linux - @tsalinger

  • [x] [Verification](https://github.com/Microsoft/vscode/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3Abug+-label%3Averified+-label%3Aduplicate+-label%3A*duplicate+-label%3Ainvalid+-label%3Aerror-telemetry+-label%3Aas-designed+milestone%3A%22February+2018%22+is%3Aclosed+)
  • All release notes updated - release notes are collected in a file named v1_21.md in this repo directory. This includes new features and notable fixes.

    • [x] @aeschli

    • [x] @alexandrudima

    • [x] @bpasero

    • [x] @chrmarti

    • [x] @dbaeumer

    • [x] @egamma

    • [x] @isidorn

    • [x] @joaomoreno

    • [x] @jrieken

    • [x] @kieferrm

    • [x] @mjbvz

    • [x] @octref

    • [x] @ramya-rao-a

    • [x] @rebornix

    • [x] @rmacfarlane

    • [x] @roblourens

    • [x] @sandy081

    • [x] @tyriar

    • [x] @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:

    • [x] vscode endgame master

    • [x] vscode-node-debug @weinand

    • [x] vscode-node-debug2 @roblourens

    • [x] vscode-debugadapter-node @weinand

    • [x] vscode-languageserver-node @dbaeumer

    • [x] language-server-protocol @dbaeumer

    • [x] vscode-textmate @alexandrudima

    • [x] vscode-loader @alexandrudima

    • [x] vscode-generator-code @aeschli

    • [x] vscode-vsce @joaomoreno

    • [ ] vscode-docs @gregvanl

    • [x] vscode-css-languageservice @aeschli

    • [x] vscode-json-languageservice @aeschli

    • [x] vscode-html-languageservice @aeschli

    • [x] jsonc-parser @aeschli

    • [ ] vscode-jscs @chrisdias

    • [x] vscode-tslint @egamma

    • [x] vscode-eslint @dbaeumer

    • [x] vscode-jshint @rmacfarlane

    • [ ] vscode-recipes @auchenberg

    • [x] localization @danyeh

    • [x] vscode-github-issues-prs @chrmarti

  • 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 change author

Friday or Monday week 2

  • [x] Disable continuous insider builds - endgame master
  • [x] Branch code to release/<x.y> and release master - endgame master
  • [x] Bump up the version in package.json - endgame master
  • [x] Announce master is open for business endgame master
  • [x] Polish release notes @gregvanl

Monday week 2 - Wednesday week 2

  • [x] Polish release notes @gregvanl
  • Cherry-pick hand-picked and reviewed changes to release/<x.y> change author
  • Build Insider from release/<x.y> endgame master
  • Manually release Insider endgame master
  • Documentation updated

    • [ ] @aeschli

    • [x] @alexandrudima

    • [x] @bpasero

    • [x] @chrmarti

    • [x] @dbaeumer

    • [x] @egamma

    • [ ] @isidorn

    • [x] @joaomoreno

    • [x] @jrieken

    • [ ] @kieferrm

    • [x] @mjbvz

    • [x] @octref

    • [x] @ramya-rao-a

    • [ ] @rebornix

    • [ ] @rmacfarlane

    • [ ] @roblourens

    • [x] @sandy081

    • [x] @tyriar

    • [x] @weinand

Thursday/Friday week 2

  • [x] Merge translations PR (if it makes it in time) endgame master
  • [x] Build stable for all platforms endgame master
  • [x] Make rpm signing request @tyriar
  • [x] Sanity check of installable bits

    • [x] Windows

    • [x] signed installer @owner

    • [x] zip @owner

    • [x] OS X - @owner

    • [x] Linux

    • [x] deb package 64-bit @owner

    • [x] deb package 32-bit @owner

    • [x] rpm package 64-bit @owner

    • [x] rpm package 32-bit @owner

    • [x] archives @owner

  • [x] Publish website @gregvanl
  • [x] Publish to stable @owner
  • [x] Publish deb and rpms to repositories manually @tyriar
  • [x] Add version with symbols to HockeyApp @tyriar
  • [x] Add a git tag to HEAD of release/<x.y> in format x.y.z endgame master
  • [x] Enable scheduled insider builds endgame master
  • [x] Twitter announcement @seanmcbreen

DONE

endgame-plan

Most helpful comment

@lynchem we're having issues with the internal service used to publish the rpm and are working with the team that owns that to resolve it. Automating this would be a huge weight off my shoulders every month but it's not currently possible.

All 5 comments

It's quite frustrating that vscode installed by rpm through the repo is notifying me of an update when it isn't available in the repo.

Perhaps code installed this way shouldn't show update notifications and leave that to the package manager (alternately speed up the upload process)

Publish deb and rpms to repositories manually

A week after release and I still don't have the Feb build available via rpm. Can this be automated for the future? Could we get the current one up there?

@lynchem we're having issues with the internal service used to publish the rpm and are working with the team that owns that to resolve it. Automating this would be a huge weight off my shoulders every month but it's not currently possible.

@Tyriar understand it can be hard but the 'an update is available' notification every time a window is opened gets frustrating, especially when I actually want to update

Was this page helpful?
0 / 5 - 0 ratings

Related issues

trstringer picture trstringer  路  3Comments

lukehoban picture lukehoban  路  3Comments

sirius1024 picture sirius1024  路  3Comments

chrisdias picture chrisdias  路  3Comments

DovydasNavickas picture DovydasNavickas  路  3Comments