VER=2.2.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
.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 new SIRF_TAG
(and STIR_TAG
etc if necessary)git push
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)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 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
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
@evgueni-ovtchinnikov can you look at the remaining SIRF ticks?
@rijobro can you do SIRF-Exercises once done with your fixes?
@paskino as soon as SyneRBI/SIRF-SuperBuild#409 is merged, you could start with the VM.
@rijobro can you do SIRF-Exercises once done with your fixes?
I've done SIRF-Exercises.
I've noticed something funny for our SB releases: https://github.com/SyneRBI/SIRF-SuperBuild/releases. It shows all tags (you might need to click "Show x newer tags"), but it states our latest release as v2.0.0, and latest pre-release as v2.1.0-rc.3, both of which are wrong.
Seems we've done something wrong in recent releases that means that these aren't getting updated. Once we figure out what it is, that should presumably go into the checklist so that we don't get it wrong again.
you have to actually "add release notes" to a tag on the releases page, otherwise GitHub won't really count it as a release, naturally. Could just copy-paste from CHANGES.md
Is there a way to do that from command line or it has to be from the github interface?
Even if it could be done on command line, it needs some thought on what to put in there. I found for instances that our SIRF CHANGES.md is a bit messy (roughly chronological order), so I've reordered text on the release page. Arguably I should have done it in CHANGES.md as well...
@paskino, can you please take care of creating the past SB releases? You have to do it in chronological order, as github doesn't do any smart ordering. (after the VM of course). Also update the SIRF checklist. Please create a maintainer issue for this.
@evgueni-ovtchinnikov could you tick the doxygen
boxes (or fix them) and close this issue then?
Closed #704.
@KrisThielemans done (actually doxygen was done a while ago but I ticked in Section 2 only)