Release management

This is a small package, so it has a simplified release management:

• master branch is supposed to be UNSTABLE and for testing
• stable releases are marked with tags of the following syntax: major.minor.revision
  • the major number is increased when there are significant jumps in functionality such as changing the framework which could cause incompatibility with interfacing systems
  • the minor number is incremented when only minor features or significant fixes have been added
  • the revision number is incremented when minor bugs are fixed

Since the master branch is a testing branch, it can be also be meant as permanent beta release. According to this fact, only RC will pretend each stable version (no alfa or beta tags).