Closed marcelm closed 1 year ago
The plan looks good.
Regarding version number, is it not big enough to merit v0.8? (I know there are more strict guide lines for version numbering though).
Definitely 0.8.0. A very popular versioning scheme is semantic versioning, which requires bumping the minor version (the 7 in 0.7.1) when adding new features. Strictly speaking, SemVer also says that you don’t have to follow that rule as long as you are pre-1.0.0, but it’s nice to do it anyway.
SemVer also wants you to always use all three components of the version number, so it would be 0.8.0 instead of 0.8.
Of course you don’t have to use SemVer, and it is sometimes not obvious how to apply its rules, but I think it’s a good start.
(And as a note for the future: You could continue to use 0ver, but I suggest you don’t ...)
I had a quick read through both SemVer and 0ver. Let us go with SemVar and version 0.8.0 for the upcoming release. I think I was trying to mimic SemVar versioning style earlier without knowing exactly what I was doing.
(0ver is a joke, not sure if that was clear.)
Haha I skimmed 0ver and was like,, "why?!", but too occupied with teaching etc to invest more time understanding, so I did not catch the joke (facepalm)
(the table of notable 0ver projects was convincing though:)
Everything is ready for the release. Shall I make one?
Let's do it! 💯
The Bioconda recipe has been merged.
Do you want to tweet/toot this, or should we fix issue #222 first? Currently, the files available for download from the release page cannot be used to compile strobealign.
Nice! I am okay with tweeting/tooting/advertising on mailing lists now that the bioconda version is updated. Will get back to you over email about the ad.
Before:
During:
git tag -a
)strobealign --version
output is correctgit push --tags
After: