Creating SMTK 21.04 Release using New Process
Preparatory steps
- Update smtk guides
- Assemble release notes into
doc/release/notes/smtk-MAJOR.MINOR.md
.-
If PATCH
is greater than 0, add items to the end of this file. -
Get positive review and merge.
-
- Assemble release notes into
Update smtk
Keep the relevant items for the kind of release this is.
If making a first release candidate from master, i.e., PATCH
is 0.
-
Update master
branch for smtk
git fetch origin
git checkout master
git merge --ff-only origin/master
-
Update version.txt
and tag the commit
git checkout -b update-to-v21.04.0 cbaf3b2f7beb38529b9941f70eb36c338357cde2
echo 21.04.0 > version.txt
git commit -m 'Update version number to 21.04.0' version.txt
git tag -a -m 'SMTK 21.04.0' v21.04.0 HEAD
-
Integrate changes.
-
Update .gitlab/ci/cdash-groups.json
to track therelease
CDash groups and commit it - Create a merge request targeting
release
-
Obtain a GitLab API token for the kwrobot.release.cmb
user (ask @ben.boeckel if you do not have one) -
Add the kwrobot.release.cmb
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)
-
-
Get positive review -
Do: merge
-
Push the tag to the main repository -
git push origin v21.04.0
-
-
-
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
-
Add (or update if PATCH
is greater than 0) version selection entry in cmb-superbuild
-
Post-release
-
Write and publish blog post with release notes. -
Post an announcement in the Announcements category on discourse.smtk.org. -
Remove deprecated methods on master
/cc @ben.boeckel /cc @bob.obara /cc @dcthomp
Edited by Robert M. O'Bara