[CCPPETMR/SIRF] SIRF Release 1.0.0 checklist (#114)

0 views
Skip to first unread message

Edoardo Pasca

unread,
Feb 13, 2018, 4:38:41 PM2/13/18
to CCPPETMR/SIRF, Subscribed

Release Checklist

VER=1.0.0

  1. SIRF
  • update CHANGES.md
  • update NOTICE.txt
  • update version numbers in SIRF/CMakeLists.txt
  • update version numbers in the doc/UsersGuide.md etc
  • git push
  • check Travis
  • run doxygen, check and upload files
  • git tag -a v$VER -m "version $VER"
  • git push origin v$VER
  1. SuperBuild
  • update CHANGES.md
  • update NOTICE.txt
  • update SIRF-Superbuild/version_config.cmake
  • run tests
  • git push
  • check Travis
  • git tag -a v$VER -m "version $VER"
  • git push origin v$VER
  1. Virtual Machine
  • update version number in VM_version.txt
  • update vb.name in vagrant/vagrantfile
  • update CHANGES.md
  • update NOTICE.txt
  • git push
  • vagrant up
  • run the zerofill trick
  • Virtualbox Guest Additions
  • export the VM and upload to website
  • git tag -a v$VER -m "version $VER"
  • git push origin v$VER

zerofill trick

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.

Kris Thielemans

unread,
Feb 13, 2018, 5:44:06 PM2/13/18
to CCPPETMR/SIRF, Subscribed

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.

Kris Thielemans

unread,
Feb 13, 2018, 5:44:21 PM2/13/18
to CCPPETMR/SIRF, Subscribed

@casperdcl do we need a docker tag step? (If so, please put it in the original checklist.md as well)

Edoardo Pasca

unread,
Feb 13, 2018, 6:01:34 PM2/13/18
to CCPPETMR/SIRF, Subscribed

@KrisThielemans you are absolutely right. Today I created a new VM to test if that worked.

Casper da Costa-Luis

unread,
Feb 13, 2018, 7:29:45 PM2/13/18
to CCPPETMR/SIRF, Subscribed

@KrisThielemans

  1. I'd really recommend 1.0.0-rc.1 since rc.1 < rc.10 but rc1 > rc10 by semver's convention
  2. I added my docker branch to milestone 1.0.0 for the SuperBuild so that the docker side of things will be completely automated by Travis. Will merge nowish.

Kris Thielemans

unread,
Feb 13, 2018, 7:51:44 PM2/13/18
to CCPPETMR/SIRF, Subscribed

sure. rc.1 is fine for me.

Kris Thielemans

unread,
Feb 15, 2018, 3:51:42 AM2/15/18
to CCPPETMR/SIRF, Subscribed

@casperdcl should we tag SIRF_data as well? I guess so

Kris Thielemans

unread,
Feb 15, 2018, 3:58:15 AM2/15/18
to CCPPETMR/SIRF, Subscribed

@paskino, please update doc/ReleaseChecklist.md according to any changes here after we're done.

Edoardo Pasca

unread,
Feb 15, 2018, 6:47:29 AM2/15/18
to CCPPETMR/SIRF, Subscribed

Only SIRF TAG is different this time?

Edoardo Pasca

unread,
Feb 15, 2018, 7:37:33 AM2/15/18
to CCPPETMR/SIRF, Subscribed

What do you reckon? The VM version can be 1.0.0? without rc.1? Or with?

Kris Thielemans

unread,
Feb 15, 2018, 7:44:37 AM2/15/18
to CCPPETMR/SIRF, Subscribed

let's leave with. then no changes presumably.
people can always update afterwards

Edoardo Pasca

unread,
Feb 15, 2018, 8:34:43 AM2/15/18
to CCPPETMR/SIRF, Subscribed

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.

Casper da Costa-Luis

unread,
Feb 15, 2018, 8:48:44 AM2/15/18
to CCPPETMR/SIRF, Subscribed

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

Casper da Costa-Luis

unread,
Feb 15, 2018, 8:53:36 AM2/15/18
to CCPPETMR/SIRF, Subscribed

ok all passed, please do continue with the checklist...

Casper da Costa-Luis

unread,
Feb 16, 2018, 6:50:31 PM2/16/18
to CCPPETMR/SIRF, Subscribed

Closed #114.

Reply all
Reply to author
Forward
0 new messages