Git Tags

[chorvus]

It would be nice to have some version tags for the official releases in the repository (eg: v1.5.4.1). Right now it's not really distinguishable whether the master branch is a stable version or not, and what version it points to.

[leo72]

I agree. I need it to checkout to previews version and check my modules compatibility.

[chorvus]

Please utilize this git feature.
The advantages are:

• Users will be able to distinguish a release commit from a mid-release commit (and potentially
• Be able to fast-forward (see upgrade) from a version to another and keep every local changes/mods easily (git will do all the magic and no manual diffing/patching is needed)
• Better overall repository organization

I also saw you created a branch with a version name which is behind the master branch. Usually there are two branching models followed:
One is when master contains every incremental change (tested), and separate features that are under construction are given their own branch. Version branches almost always indicate future versions worked on.
The other one is the well known master/develop/feature branching model described here: http://nvie.com/posts/a-successful-git-branching-model/ (there are some variations around too).

The first one is easier to follow but overall less organized, but it's still an upgrade towards the current one.
A large scale project such this would benefit from switching to either one of them, along with the taging of the commits.

Keep up the good work and don't stop learning :)
Alex

[rb2]

Duplicates #398 and #151