Tagging release 0.6
ckandoth opened this issue · 3 comments
I am going to tag the current master
branch as release 0.6
. The recent commit 2c62cc9 seems important, and we want to start using it in our research pipeline. I will include a Dockerfile. Let me know if you have any concerns.
I updated version numbers in source/docs, updated the Dockerfile, updated the linux binary, and tagged a 0.6
release. I am unable to update the OSX binary without immediate access to an OSX machine. But I'll leave this ticket open till I am able to do that, and then add a new commit that tag 0.2
will point to.
Thanks Cyriac for releasing 0.6 and made a Dockerfile. The commit 2c62cc9 fixed or added 1.4% MS sites across the whole human genome in scan step.
I was unable to make a macos binary - so I decided to remove the binaries altogether - and attach them to the releases instead - https://github.com/ding-lab/msisensor/releases - this will allow us to add binaries later, without having to add commits or moving tags. Release 0.6 should be good to go.