Our version number syntax is: major.minor.micro status statusVersion
status is considered "Release" when omitted.
statusVersion is optional, but ignored when status is "Release"
4.1.0 Alpha 4
For the newly added Candy and inVerse clients, I'd like to have version numbers that reflect the upstream version number of the Candy release that our plugin is based on.
2.2.0 Release 1 - our first plugin that is based on Candy 2.2.0
2.2.0 Release 2 - our second plugin that is based on Candy 2.2.0
2.3.0 Release 1 - our next plugin, after upgrading Candy to version 2.3.0
For this to work, I'd like to be able to specify a statusVersion, even when status is "Release"