The curator tool, which we use to publish libmongocrypt packages into a PPA for users to be able to install, recognizes version numbers in the following way:

• contains 'rc' -> is a release candidate (testing)
• contains '-' and is not a release candidate -> is a development build
• all others -> is a release build

The way that GetVersion.cmake produces version numbers needs to be adjusted so that non-release and non-rc builds are always recognized as development builds by curator. That is, a version strategy is required where development builds take the last release version, increment the patch component, append '-dev', and then append the additional build information we prefer to have (currently build date and git commit hash).