Yes, it is quite confusing, sorry. This is the current situation:
- Before we release Defold, we bump the version (e.g. 1.2.99) which is stored in a file. The specific git sha1 of that release is what people are able to download.
- Editor2 reads the version from the same file, which is unchanged for the coming two weeks. However, Editor2 is released for every commit made on the dev-branch, both editor and engine.
- This means that Editor2 will ship every new engine feature as well being developed during the two weeks. It is bleeding-edge so to speak, but fooling you that it’s the same version (e.g. 1.2.99). But as you noted, it’s the git sha1 that really matters.
It is a temporary thing to release editor2 like that, and the purpose is to ship bug-fixes at top speed. In a few weeks, the bug count should be down and we will let it follow the regular two-week cycle.