Release checklist

• Make sure tests on travis pass.
• Bump version at https://github.com/iterative/dvc/blob/master/dvc/__init__.py. Name your commit as dvc: bump to 0.54.3, so it is easier to look for old releases in git log by searching for the keyword bump.
• Go to https://github.com/iterative/dvc/releases.
  1. click “Draft a new release”.
  2. name tag and version the same as in 1), e.g. 0.17.1.
  3. add a changelog to the comments to the release. See https://github.com/iterative/dvc/releases/tag/0.53.2 for an example. Be sure to insert links to the issues closed and be sure to give kudos to outside contributors.
  4. click “Publish release”.
• Wait until build on travis is passing successfully.
• Travis will deploy packages to pypi and binary packages to the corresponding github release page automatically if all tests and pkg builds pass.
• Go to https://github.com/iterative/dvc.org/blob/master/src/components/DownloadButton/index.tsx and update downloadlinks. Name your commit as download: update to 0.54.3.
• Go to https://github.com/iterative/lambda-latest-version/blob/master/lambda_function.py, update dvc version and name your commit as lambda: update to 0.54.3. Travis will deploy to aws automatically.
• Brew guys seem to now update our package automatically, but please keep an eye on it https://github.com/Homebrew/homebrew-core/blob/master/Formula/dvc.rb
• Update https://github.com/iterative/chocolatey-dvc/blob/master/tools/chocolateyinstall.ps1 and https://github.com/iterative/chocolatey-dvc/blob/master/dvc.nuspec . Choco moderation process takes a while, so don't wait for it, but do babysit https://chocolatey.org/packages/dvc , since their test suit is flaky. We are trying to get a trusted status right now so we don't have to suffer.
• Our deb and rpm repos will be updated automatically by travis once a day based on dvc.org/latest.
• Conda bots will automatically create a PR in dvc-feedstock when dvc is updated on pypi. Be sure to follow the instructions in the PR before merging it. For additional info see https://github.com/iterative/dvc/wiki/Maintenance-of-Anaconda-package-in-conda-forge-channel

Major version transitions

1. request a new channel version-prefix (aka track) at https://forum.snapcraft.io/t/track-request-for-dvc/17735 (e.g. v2)
   • otherwise attempting to snapcraft release --channel=v2 will fail
2. create a new legacy-dev git branch (e.g. 1.x-dev)
3. (optional) give a warning message: cherry-pick dvc@6f0a05ad. Wait ~30 days before continuing to the next step
   • the idea is to warn & give 2 options: opt-in now, or opt-out permanently. Both options will suppress the warning. Ignoring the warning will result in an auto-upgrade in 30 days
4. uncomment the echo "unset SNAP_CHANNEL" >>env.sh line in scripts/ci/before_install.sh