Release checklist

Things that need to happen before we make a public release announcement

• Error handling and debugging - #470
• Update Details section, changelog, get started - https://github.com/iterative/vscode-dvc/issues/434, https://github.com/iterative/vscode-dvc/issues/435
• Document that we collect telemetry information and users can opt-out by setting telemetry.enableTelemetry to false (https://github.com/iterative/vscode-dvc/issues/511#issuecomment-913986086).
• Ask VS Code to prompt the user to install our extension when “dvc.yaml” or “dvc.lock” or “.dvc” file is present
• Investigate walkthroughs
• Add plots into walkthrough
• Check everything in walkthrough is up to date and correct (#1876)
• Make repo public
• Remove preview tag from extension (#1860)
• README = marketplace listing -> the existing one needs to be reworked (#1816)
• Add extra badges once the repo is public (https://shields.io/) (#1873)
• Add repo banner (#1875)
• Make sure VS Code is added to DVC README (https://github.com/iterative/dvc/pull/7859)
• Add to iterative README (https://github.com/iterative)
• Verify Iterative as a publisher
• Release pipeline (#754)
• Publish to Open VSX from the pipeline https://github.com/iterative/vscode-dvc/issues/1595
• Internal alpha testing
• Early adopter testing
• Minification of code / Tree shaking (optional) - won’t do
• Implement light theme design (light svgs https://github.com/iterative/vscode-dvc/issues/175#issuecomment-876951701) - won’t do
• Consider extension pack (Yaml parser, vscode-cml and whatever the dvc-azure plugin is called) - consider later
• Revisit Restricted Mode with a walkthrough explanation and/or allowing limited capability
• Rename master to main
• Automate changelogs
• Create marketplace release checklist - won’t do, after release has been further automate we can release more often instead
• Check dependency licenses
• Test against arbitrary large repo (https://github.com/iterative/vscode-dvc/issues/429#issuecomment-1082458061) - done for now

Won’t do

• Rework of data management code after dvc status is released
• E2E tests

[mattseddon]

Current list of Licenses:

❯ npx license-checker --summary 
npx: installed 58 in 1.577s
├─ MIT: 1554
├─ ISC: 137
├─ BSD-3-Clause: 102
├─ BSD-2-Clause: 41
├─ Apache-2.0: 36
├─ (MIT OR CC0-1.0): 4
├─ CC0-1.0: 3
├─ MPL-2.0: 3
├─ Unlicense: 3
├─ MIT*: 3
├─ CC-BY-4.0: 2
├─ WTFPL: 2
├─ 0BSD: 2
├─ (Unlicense OR Apache-2.0): 1
├─ Python-2.0: 1
├─ (MIT OR Apache-2.0): 1
├─ Custom: http://github.com/substack/node-bufferlist: 1
├─ UNLICENSED: 1
├─ LGPL-3.0: 1
├─ (MIT OR WTFPL): 1
├─ BSD*: 1
├─ (Apache-2.0 OR MPL-1.1): 1
├─ ODC-By-1.0: 1
├─ (BSD-3-Clause OR GPL-2.0): 1
├─ (MIT AND Zlib): 1
├─ (WTFPL OR MIT): 1
├─ (BSD-2-Clause OR MIT OR Apache-2.0): 1
├─ (MIT AND BSD-3-Clause): 1
├─ (BSD-2-Clause OR WTFPL): 1
├─ CC-BY-3.0: 1
└─ (MIT OR GPL-3.0): 1

http://github.com/substack/node-bufferlist - MIT

👍🏻 good to go.

[mattseddon]

Related to publishing to Open VSX - https://github.com/EclipseFdn/open-vsx.org/issues/1024