It occurs to me that gems we release will still have `@DEVELOPMENT_VERSION@` in lib/mcollective.rb, given that the packaging repo's version file update automation is only called when producing a tarball [[1]](https://github.com/puppetlabs/packaging/blob/master/tasks/tar.rake#L75). Though this appears to have always been the case with mcollective, is it worth revisiting now to ensure the gem has the correct version in lib/mcollective.rb?