Release methodology

This is just an overview as to how I'm currently handling releases of the php-opencloud bindings:

• All ongoing development takes place in the Master branch. Thus, master is always the most up-to-date, but has the possibility of being unstable (the goal is for master to be always stable, however).
• When a certain feature set or level of stability is reached, the version number (in globals.php) is incremented and a new release is tagged. You can download specific releases from the Tags page.
• smoketest.php is run before accepting any new pull requests or code commits. This does not exhaustively test every feature (we're trying to develop integration tests that will do that), but it does test all the major functionality and should let us know if we broke something with a change.