Please Tag Releases

[dovy]

It's great that you use github, but could you tag the "stable" releases please? That would sure help services know what's stable and what's not. ;)

[lelandriordan]

I completely agree with @dovy. It is too hard to follow all the updates as it currently stands, let alone differentiate between things like minor fixes and important security patches. Now that _s has thousands of themes based on itself this is a problem.

Something like semver and a changelog needs to be implemented following the conventions used by Atom and Bootstrap. The master branch is like the work in progress branch with all of the latest commits. And then there should be semantically versioned tagged releases that are stable. The downloader on underscores.me should use the latest tagged release, while developers using git can clone the repo and use whatever version they want via git checkout

[dovy]

Agreed, but even if branches aren't used, tags are essential.

[kraftbj]

This post explains the rationale for going versionless: http://themeshaper.com/2013/10/11/dont-update-your-theme/

The versions, previously, were relatively random and didn't mean much. Everything committed to master is ready to be used as part of a starter theme.

[philiparthurmoore]

Please see #182.