[Docs] Update some docs for 1.0

Author: bbatsov

README.md

@@ -133,21 +133,9 @@ core team members. Lovingly known as The Alumni:
 
 ## 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`.
+We’re following [SemVer](http://semver.org/).
+
+You can read more on the subject [here](https://docs.cider.mx/cider/about/release_policy.html).
 
 ## Logo
 

doc/modules/ROOT/pages/about/compatibility.adoc

@@ -18,7 +18,7 @@ and Boot releases.
 == Java
 
 CIDER officially targets Java 8, Java 11 and the most recent rapid
-release version (e.g. Java 13).  More generally speaking - we aim
+release version (e.g. Java 15).  Generally speaking, we aim
 to support all Java releases that are currently officially supported
 by Oracle.
 
@@ -89,6 +89,13 @@ Below you can find the official compatibility matrix for CIDER.
 | 8
 | 1.8
 
+| 1.0
+| 25.1
+| 0.6
+| 0.25
+| 8
+| 1.8
+
 |===
 
 TIP: You can also check the requirements of a particular CIDER version by inspecting

doc/modules/ROOT/pages/about/release_policy.adoc

@@ -1,24 +1,25 @@
 = Release Policy
 
-We're following http://semver.org/[SemVer] (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).
+We're following http://semver.org/[SemVer].
+
+NOTE: Prior to CIDER 1.0, bumps of the minor (second) version number
+were considered major releases (e.g. 0.25 and 0.26 were major
+releases).
 
 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.
+never contain new features or public API changes.
 
 Here are a few examples:
 
-* 0.5.0 - Feature release
-* 0.5.1 - Bug-fix release
-* 0.5.2 - Bug-fix release
-* 0.6.0 - Feature release
+* 1.1.0 - Feature release
+* 1.1.1 - Bug-fix release
+* 1.1.2 - Bug-fix release
+* 1.2.0 - Feature release
 
-CIDER and cider-nrepl are released independently, but follow the same release policy overall.
+CIDER and cider-nrepl are released independently, but follow the same release policy overall.footnote:[Keep in mind, though, that cider-nrepl has yet to make it to version 1.0]
 CIDER contains references to the cider-nrepl version it supports and would normally inject
 the newest cider-nrepl version possible.
+
+Commands that were made obsolete will be removed in the next major release.