Semantic versioning + tagging releases

[misscs]

Vision

• Tag each release following semantic versioning guidelines.
• Maintain a release log using Github. This is a great example from NPM project

The goal of tagging releases is to:

1. Provide a clear overview of changes
2. Provide clearer path to contribution
3. Organize major releases (ex. name branches after the release and ability to use labels or milestones in issue tracker to group by major release)
4. Easier to release updates incrementally and roll back if necessary