Closed evgueni-ovtchinnikov closed 3 years ago
Set version variable of the release for further steps using the format
VER=3.0.0-rc.1
git submodule update
cd data && git tag -a v$VER -m "version $VER" && git push --tags && cd ..
git status
data
CHANGES.md
NOTICE.txt
.zenodo.json
git push
git tag -a v$VER -m "version $VER"
git push origin v$VER
SIRF-Superbuild/version_config.cmake
SIRF_TAG
STIR_TAG
vb.name
vagrant up
first_run.sh
SIRF 2.2.0.ova
-release-candidate-1
rc1
git clone https://github.com/SyneRBI/SIRF.wiki.git; cd SIRF.wiki
git clone https://github.com/SyneRBI/SyneRBI_VM.wiki.git; cd SyneRBI_VM.wiki
closing as we'll proceed with 3.0.0
Release Checklist
Set version variable of the release for further steps using the format
git submodule update
# should not complaincd data && git tag -a v$VER -m "version $VER" && git push --tags && cd ..
git status
# should not listdata
as modifiedCHANGES.md
NOTICE.txt
.zenodo.json
git push
git tag -a v$VER -m "version $VER"
git push origin v$VER
CHANGES.md
NOTICE.txt
SIRF-Superbuild/version_config.cmake
with newSIRF_TAG
(andSTIR_TAG
etc if necessary)git 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
vb.name
in vagrant/vagrantfileCHANGES.md
NOTICE.txt
git push
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 whatrc1
means).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
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
git clone https://github.com/SyneRBI/SyneRBI_VM.wiki.git; cd SyneRBI_VM.wiki
(or pull)git tag -a v$VER -m "version $VER"
git push origin v$VER