Closed gaurav closed 3 years ago
It's not supposed to be a mistake: in Maven, the development version is conventionally x.(y+1)-SNAPSHOT
, which I applied literally to get a development version of 1.2.0-SNAPSHOT
. I could also have used 1.1.1-SNAPSHOT
or 2.0.0-SNAPSHOT
-- the key thing is that the SNAPSHOT
indicates code that is still in development. Which of those do you think would be best?
Since we needed to release 1.1.1
, I have to change the version number to that for this release, but then I'll change it back to 1.2.0-SNAPSHOT
once I'm done. Depending on what changes we make in the future, our next JPhyloRef release could be 1.1.2
, 1.2.0
or 2.0.0
, but conventionally the development version should be 1.2.0-SNAPSHOT
until we prepare the next release.
conventionally the development version should be
1.2.0-SNAPSHOT
until we prepare the next release
Sounds good and makes sense!
This PR is intended to release JPhyloRef v1.1.1. The only difference from v1.1.0 is some minor changes to the JOSS manuscript.
As with previous releases, once this PR has been reviewed, I will publish it to the Sonotype Maven repository, tag it and publish it to Zenodo. Once that's done, I'll update the paper to refer to the latest version of JPhyloRef in Zenodo, increment the version number, add
-SNAPSHOT
back to the version number, and merge these changes back intomaster
.