Versions, branches and tags

Spring Lemon adheres to the following rules:

1. Create a new git branch, e.g. 0.9, out of master.
2. Checkout that branch.
3. Update the version number in pom to 0.9.0
4. Do the development
5. Test it out
6. Create a git tag, named 0.9.0, to be released as the latest stable code
7. Merge 0.9 to master
8. Create a new branch, 0.10 (or 1.0), and repeat the process above

While development will be going in 0.10 branch, if we need to do some fix in the released 0.9.0,

1. Checkout 0.9
2. Update the version number in pom to 0.9.1
3. Do the development
4. Test it out
5. Create a git tag, named 0.9.1, to be told to the users as the latest stable code
6. Merge 0.9 to master, and pull the master into 0.10