Mark release as beta

Fix for #71.

How it work?

* new option is added - ```label```. It have 3 choices (RC, beta, alpha, none). If none is choosen then new version will be without label. 

example workflow:

```
Current version: 0.0.0
type: p
label: a
Next Version: 0.0.1-alpha

Current version: 0.0.1-alpha
type: p
label: a
Next Version: 0.0.1-alpha2

Current version: 0.0.1-alpha2
type: p
label: b
Next Version: 0.0.1-beta

Current version: 0.0.1-beta
type: p
label: n
Next Version: 0.0.1

Current version: 0.0.1
type: p
label: n
Next Version: 0.0.2

Current version: 0.0.b
type: m
label: b
Next Version: 1.0.0-beta

```

Any help with this is welcome. 
Yeah i would avoid that if it's possible. Latest stable in the 2.x branch is 2.1.0, if this is good enough i would use a ~2.0 constraint, otherwise you should ask for a new stable release

2.1.0 released on Sep 20, 2013 · 25 commits to master since this release