VER=1.0.0
CHANGES.md
NOTICE.txt
git push
git tag -a v$VER -m "version $VER"
git push origin v$VER
CHANGES.md
NOTICE.txt
SIRF-Superbuild/version_config.cmake
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
git tag -a v$VER -m "version $VER"
git push origin v$VER
sudo dd if=/dev/zero of=/EMPTY bs=1M
sudo rm -f /EMPTY
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
thanks @paskino.
I've changed the version number to 1.0.0-rc1. no need to change this for the VM I think.
I cannot see how you can create the final VM before all the stuff above is ticked though... Seems to me you need to untick from vagrant up
. or you could choose the update it I guess.
@casperdcl do we need a docker tag step? (If so, please put it in the original checklist.md as well)
@KrisThielemans you are absolutely right. Today I created a new VM to test if that worked.
1.0.0-rc.1
since rc.1 < rc.10
but rc1 > rc10
by semver's conventionsure. rc.1
is fine for me.
@casperdcl should we tag SIRF_data as well? I guess so
@paskino, please update doc/ReleaseChecklist.md according to any changes here after we're done.
Only SIRF TAG is different this time?
What do you reckon? The VM version can be 1.0.0? without rc.1? Or with?
let's leave with. then no changes presumably.
people can always update afterwards
There's a travis error https://travis-ci.org/CCPPETMR/SIRF-SuperBuild/jobs/341865694 which is related to a network problem rather than our software.
It's merged in now (#90) and @KrisThielemans deleted the branch which is why the PR build failed. master
seems to be building fine though apart from https://travis-ci.org/CCPPETMR/SIRF-SuperBuild/jobs/341868335 which I just restarted
ok all passed, please do continue with the checklist...
Closed #114.