Release for Joss + versioning strategy

[antonio-leblanc]

Essential Actions for JOSS Submission

• Finish the joss paper Joss paper #76 and merge it to master
• Tagged Release: Create a specific version tag in Git for the ForeFire software state we are submitting (we can discuss on the version of the include/version.h file
• Software Archive & DOI: This tagged release needs to be archived on Zenodo (or figshare). This will give us a new DOI

Versioning of forefire in general

• we can put the increment version script only on master, although it is also usefull to have it in dev in case dev is broken we can easily find the latest working version
• when creating the version for Joss submission filippi will decide which he prefers

[antonio-leblanc]

https://github.com/forefireAPI/forefire/releases/tag/v2.0

[antonio-leblanc]

openjournals/joss-reviews#8680