Release 9.1.0
Update VTK
- Update the local copy of
release
.- If
0
is0.rc1
, updatemaster
- Otherwise, update
release
- If
git fetch origin
git checkout release
git merge --ff-only origin/release # if this fails, there are local commits that need to be removed
git submodule update --recursive --init
- If `release` is not `master`, ensure merge requests which should be
in the release have been merged. The [`backport-mrs.py`][backport-mrs]
script can be used to find and ensure that merge requests assigned to the
associated milestone are available on the `release` branch.
- Make a commit for each of these changes on a single topic (suggested branch
name:
update-to-v9.1.0
):- Assemble release notes into
Documentation/release/9.1.md
.-
If PATCH
is greater than 0, add items to the end of this file.
-
-
If release
ismaster
, update the non-patch version in a separate commit (so thatmaster
gets it as well). -
Remove old release note files -
Update .gitlab/ci/cdash-groups.json
to track therelease
CDash groups -
Update CMake/vtkVersion.cmake
and tag the commit (tag this commit below)
- Assemble release notes into
$EDITOR CMake/vtkVersion.cmake
git commit -m 'Update version number to 9.1.0' CMake/vtkVersion.cmake
- Create a merge request targeting
release
-
Obtain a GitLab API token for the kwrobot.release.vtk
user (ask @ben.boeckel if you do not have one) -
Add the kwrobot.release.vtk
user to your fork with at leastDeveloper
privileges (so it can open MRs) -
Use the release-mr
script to open the create the Merge Request (see script for usage)- Pull the script for each release; it may have been updated since it was last used
- The script outputs the information it will be using to create the merge request. Please verify that it is all correct before creating the merge request. See usage at the top of the script to provide information that is either missing or incorrect (e.g., if its data extraction heuristics fail).
-
Get positive review -
Do: merge
-
Push the tag to the main repository -
git tag -a -m 'VTK 9.1.0' v9.1.0 commit-that-updated-vtkVersion.cmake
-
git push origin v9.1.0
-
-
- Gather release assets
-
Source (from the build:source
CI job in the tag pipeline) -
Documentation (from the release-prep:documentation
CI job in the tag pipeline) -
Wheels (from the build:wheel-*
jobs).
-
- Upload assets to
vtk.org
-
rsync -rptv $tarballs $wheels user@host:vtk_release/9.1/
-
-
Update vtk.org/download
with the new release (emailcomm@kitware.com
with filenames and hashes) - Software process updates (these can all be done independently)
-
Update kwrobot with the new release
branch rules (@ben.boeckel) -
Run this script to update the CDash groups - This must be done after a nightly run to ensure all builds are in the
release
group - See the script itself for usage documentation
- This must be done after a nightly run to ensure all builds are in the
-
Post-release
-
Post an announcement in the Announcements category on discourse.vtk.org.
/cc @ben.boeckel /cc @ken-martin /cc @utkarsh.ayachit