We currently version Stencyl using the number of commits that have been made to the source code. This is a holdover from our early development workflow, years ago.
Since we have branches now, that build number alone isn't enough to uniquely identify which version of Stencyl is being used. We don't make it very clear, either, that this isn't really useful information.
For example, say we released Stencyl 4.0.0 with build number 40000. Then we make 20 changes to the public release branch and release Stencyl 4.0.1 as build 40020. The trouble is, in the meantime we've made 60 changes to the private builds, so within that lineup, we have another build 40020 that contains completely different changes.
Here's how we're changing this going forward.
For people using a public release, they just see the release version. (4.0.1, 4.0.2, 4.1.0, etc.)
For people using a mainline private build, they see the version and build number. Additionally, the version will always be at least a minor step up from the public releases, and contain the beta qualifier. (4.2.0-beta b10480, 4.2.0-beta b10500, etc.)
For people using one of the feature branches which haven't even been folded in to the mainline private builds, they'll additionally see the name of the branch. (e.g. 4.2.0-beta [attr-type-extension] b10430)
This info will be present in these locations:
Since we have branches now, that build number alone isn't enough to uniquely identify which version of Stencyl is being used. We don't make it very clear, either, that this isn't really useful information.
For example, say we released Stencyl 4.0.0 with build number 40000. Then we make 20 changes to the public release branch and release Stencyl 4.0.1 as build 40020. The trouble is, in the meantime we've made 60 changes to the private builds, so within that lineup, we have another build 40020 that contains completely different changes.
Here's how we're changing this going forward.
For people using a public release, they just see the release version. (4.0.1, 4.0.2, 4.1.0, etc.)
For people using a mainline private build, they see the version and build number. Additionally, the version will always be at least a minor step up from the public releases, and contain the beta qualifier. (4.2.0-beta b10480, 4.2.0-beta b10500, etc.)
For people using one of the feature branches which haven't even been folded in to the mainline private builds, they'll additionally see the name of the branch. (e.g. 4.2.0-beta [attr-type-extension] b10430)
This info will be present in these locations:
- Title bar
- Help Menu
- Log output
