Version Strategy for Boilerplate

Summary

At the moment there are no Git tags or other markers in the repo to declare any sort of versioning. On a related note, there is no established Changelog to see how the boilerplate is changing.

Details

A developer may want to be able to spin off multiple new repositories using older versions of the boilerplate instead of always the tip commit of master/develop branch. They may have requirements for older versions of Gradle or of some of the dependencies. At the moment they would have to scan through the commit history as there are no clear delineations about iterations of the boilerplate.

This would also help as you look to automate the process of instantiating a new repo based off the boilerplate.

Other Notes

I'd also recommend considering the following:

• Establishing what is left to do before considering the boilerplate 1.0 (i.e. set a milestone) versus what could/should be done later.
• Adding any versioning strategy to your Contributing.md file.
• Automating the process of "releasing" a new version of the boilerplate (e.x. https://github.com/ustwo/github-scanner/blob/master/.github/CONTRIBUTING.md#release )