How should releases be done, including versioning?

[jbphet]

I'm about to publish the first version of this app to the Play Store for internal testing, and I'm thinking I should document the process so that I can make it repeatable. When releasing a PhET sim, we have a lot of support from the tools that we've built up of the years, but I can't use them for this process. I'm going to write the steps up as a manual checklist in the doc directory, and may add some support in the form of grunt tasks once this is a bit more established.

[jbphet]

I'll use the same versioning system that PhET is using, which is called "Semantic Versioning" and is described here. It has numbers for major, minor, and patch releases, e.g. 1.0.2. I'm going to start with version 0.0.1, since this is very much a beta release.

[jbphet]

The release process will be described in this document, at least for now.

[jbphet]

I've created the first version of the checklist document. I'll leave this issue open but anassigned for now, and will make an effort to update the list when future releases are published.