-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Release checklist
Ruslan Kuprieiev edited this page Oct 23, 2020
·
41 revisions
- 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 ingit log
by searching for the keywordbump
. - Go to https://github.com/iterative/dvc/releases and edit an existing release draft, name tag and version the same as in 1), e.g.
0.17.1
. - GHA will deploy packages to pypi and binary packages to the corresponding github release page automatically.
- Go to https://github.com/iterative/dvc.org/blob/master/src/components/DownloadButton/index.tsx and update
downloadlinks
. Name your commit asdownload: update to 0.54.3
. - 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.
- 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
- 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 deb/rpm to aws automatically.
- 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
- otherwise attempting to
- create a new legacy-dev git branch (e.g.
1.x-dev
) - (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
- uncomment the
echo "unset SNAP_CHANNEL" >>env.sh
line inscripts/ci/before_install.sh