summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorBozhidar Batsov <bozhidar@batsov.com>2014-08-09 12:47:29 +0300
committerBozhidar Batsov <bozhidar@batsov.com>2014-08-09 12:47:29 +0300
commitb394977bc2c286032c5723cfdc14b71997e2af29 (patch)
tree3ea1042a882736e9d227f9ada90c530c66d5ed39 /README.md
parent2ea95211039d97da6ef03857da10ba4ad0c9b993 (diff)
Document the release policy
Diffstat (limited to 'README.md')
-rw-r--r--README.md17
1 files changed, 17 insertions, 0 deletions
diff --git a/README.md b/README.md
index cf791349..0ed37aae 100644
--- a/README.md
+++ b/README.md
@@ -756,6 +756,23 @@ An extensive changelog is available [here](CHANGELOG.md).
* [Steve Purcell](https://github.com/purcell)
* [Jeff Valk](https://github.com/jeffvalk)
+## Release policy
+
+We’re following [SemVer](http://semver.org/) (as much as one can be
+following it when the major version is 0). At this point bumps of the
+minor (second) version number are considered major releases and always
+include new features or significant changes to existing features. API
+compatibility between major releases is not a (big) concern (although we try
+to break the API rarely and only for a good reason).
+
+The development cycle for the next major
+release starts immediately after the previous one has been
+shipped. Bugfix/point releases (if any) address only serious bugs and
+never contain new features.
+
+The versions of CIDER and `cider-nrepl` are always kept in sync. If you're tracking the
+`master` branch of CIDER, you should also be tracking the `master` branch of `cider-nrepl`.
+
## Logo
CIDER's logo was created by [@ndr-qef](https://github.com/ndr-qef). You can find the logo in various