Include exporter version in 'generator' string.

Will likely be helpful down the road if assets include the version of the exporter used. I.e. replace Khronos Blender glTF 2.0 exporter with Khronos Blender glTF 2.0 exporter (<version>), where <version> is either a commit hash or semver version.

[emackey]

@pjoe and I were talking about this on the KhronosDev #gltf channel.

There’s a file convert_to_strict_2.80.py that could potentially be used to write a git SHA1 value into a version string someplace.

But, Blender addons do use SemVer, not SHA1s, and we’ve had the 0.0.1 version for far too long. I think it’s well past time to at least declare 1.0.0 on what we have now. We could then be more rigorous about incrementing the number with each major PR, or with each copy to Blender.

Also, it looks like the generator string was never updated to include the version number. That would be a great thing to start doing right away, especially as we are seeing more sample output being submitted with bug reports.

[donmccurdy]

I think I’d vote to bump the version when we submit an update to the Blender repo. Using https://semver.org/ seems as good as anything, unless the Blender project has another system? We can add a version.sh script to automate this if needed.