Set version variable of the release for further steps, e.g. using the format
VER=3.8.0
git submodule update
# should not complaincd data && git tag -a v$VER -m "version $VER" && git push --tags && cd ..
git status
# should not list data
as modifiedCHANGES.md
NOTICE.txt
CITATION.cff
git push
git tag -a v$VER -m "version $VER"
git push origin v$VER
CHANGES.md
NOTICE.txt
CITATION.cff
SIRF-Superbuild/version_config.cmake
with new SIRF_TAG
(and STIR_TAG
etc if necessary)vb.name
in vagrant/vagrantfilegit push
git tag -a v$VER -m "version $VER"
git push origin v$VER
git tag -a v$VER -m "version $VER"
git push origin v$VER
vagrant up
first_run.sh
script (gnome settings and zero-fill trick)SIRF 2.2.0.ova
(with space) as Zenodo uses alphabetical ordering probably, add -release-candidate-1
if necessary (as most people will not know what rc1
means).git tag -a v$VER -m "version $VER"
git push origin v$VER
git clone https://github.com/SyneRBI/SIRF.wiki.git; cd SIRF.wiki
(or pull)git tag -a v$VER -m "version $VER"
git push origin v$VER
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
@KrisThielemans any updates in SIRF NOTICE.txt and CITATION.cff? If none, I can tag and release SIRF today.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.