Release 1.6.0-rc1
Update VTKm
-
Update release
branch for vtk-m and create update branch
git fetch origin
git checkout release
git merge --ff-only origin/release
git submodule update --recursive --init
git checkout -b update-to-1.6.0-RC1
-
Bring as a second parent the history of master
git merge --no-ff origin/master
-
Craft or update docs/changelog/X.Y/release-notes.md
file -
Create release notes commit
git add docs/changelog/X.Y/release-notes.md
git rm docs/changelog/*.md
git commit -m 'Add release notes for 1.6.0-RC1
-
echo 1.6.0-RC1 > version.txt
-
Create commit with the following template
git commit -m '1.6.0-RC1 7th official release of VTK-m.
The major changes to VTK-m from 1.5.1 can be found in:
docs/changelog/1.6.0/release-notes.md'
-
git tag -a -m 'VTKm 1.6.0-RC1' v1.6.0-RC1 HEAD
- Integrate changes to
master
branch-
Create a merge request targeting master
(do not addBackport: release
) -
Do: merge
-
- Integrate changes to
update
branch (push theupdate-to-1.6.0-RC1
branch to be the newrelease
branch)-
git push origin update-to-v1.6.0-RC1:release
-
- Push tags
-
git push origin v1.6.0-RC1
-
Spack
-
Update Spack package: https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/vtk-m/package.py
Post-release
-
Copy the contents of docs/changelog/X.Y/release-notes.md to the GitLab release -
Post an email announcement on VTK-m mailing list.
/cc @ben.boeckel
/cc @vbolea
Edited by Vicente Bolea