better versioning system

BindaCMS · Feb 6, 2018 · 85fa22f · 85fa22f
1 parent fa053a3
commit 85fa22f
Show file tree

Hide file tree

Showing 3 changed files with 19 additions and 2 deletions.
diff --git a/Gemfile.lock b/Gemfile.lock
@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    binda (0.1.6)
+    binda (0.1.6.alpha.1)
       aasm (>= 4.11, < 4.13)
       ancestry (>= 2.1, < 3.1)
       bourbon (= 4.3.4)

diff --git a/README.md b/README.md
@@ -934,6 +934,23 @@ Same thing can be done on linux usign another binary code (see [documentation](h
 
 
 
+# Binda versioning
+
+It's possible to test edge versions of Binda on real projects. Edge versions can be found only in the github repository and can be referenced by tag.
+
+For example once `v0.1.0` is published any new edge release which can be considered stable enough for a real project is tagged with alpha or beta (`v0.1.1.alpha`, `v0.1.1.alpha.1`, `v0.1.1.beta`, etc). These tags won't change and won't be removed so you can safely add them to you gemfile like so:
+
+```ruby
+gem 'binda', github: 'lacolonia/binda', ref: 'v0.1.1.alpha.1'
+```
+
+The same tag is listed as the gem version, but it's not published to Rubygems.
+
+More info can be found at the [semantic versioning documentation](https://semver.org/spec/v2.0.0-rc.1.html).
+---
+
+
+
 ### Bug reporting
 Please refer to this [guide](http://yourbugreportneedsmore.info).
 If you need direct help you can join [Binda Slack Community](https://bindacms.slack.com).

diff --git a/lib/binda/version.rb b/lib/binda/version.rb
@@ -1,3 +1,3 @@
 module Binda
-  VERSION = '0.1.6'.freeze
+  VERSION = '0.1.6.alpha.1'.freeze
 end