fVersion is a list with 4 members. The 3rd is documented as "build type". However, when a module is created in CSIDE the opportunity to create a version number is limited to the 1st, 2nd & 4th members.
Is the "build type" simply ignored? I'd like to be able to use it to move from development to release if possible. So versioning would be something like "1.0d0 -> 1.0d1 -> 1.0d2 -> 1.0r0 -> 1.1d0" where the module upgrader recognises the change.
This is preferable to simply overwriting module directories in $OTHOME on test systems.
Possible or not?
