Prepare for release

[ci skip]

README.md

@@ -7,6 +7,7 @@ A collection of classes to work with GIS geometries.
 
 [![Build Status](https://secure.travis-ci.org/brick/geo.svg?branch=master)](http://travis-ci.org/brick/geo)
 [![Coverage Status](https://coveralls.io/repos/brick/geo/badge.svg?branch=master)](https://coveralls.io/r/brick/geo?branch=master)
+[![Latest Stable Version](https://poser.pugx.org/brick/geo/v/stable)](https://packagist.org/packages/brick/geo)
 [![License](https://img.shields.io/badge/license-MIT-blue.svg)](http://opensource.org/licenses/MIT)
 
 Introduction
@@ -28,14 +29,27 @@ Just define the following requirement in your `composer.json` file:
 
     {
         "require": {
-            "brick/geo": "dev-master"
+            "brick/geo": "0.1.*"
         }
     }
 
 Then head on to the [Configuration](#configuration) section to configure a GIS geometry engine.
 
 Failure to configure a geometry engine would result in a `GeometryEngineException` being thrown when trying to use a method that requires one.
 
+Project status & release process
+--------------------------------
+
+This library is still under development.
+
+The current releases are numbered `0.x.y`. When a non-breaking change is introduced (adding new methods, optimizing existing code, etc.), `y` is incremented.
+
+**When a breaking change is introduced, a new `0.x` version cycle is always started.**
+
+It is therefore safe to lock your project to a given release cycle, such as `0.1.*`.
+
+If you need to upgrade to a newer release cycle, check the [release history](https://github.com/brick/geo/releases) for a list of changes introduced by each further `0.x.0` version.
+
 Configuration
 -------------