add a release guide

Even though there are very few steps involved, it is good to have it documented.

RELEASE.md

@@ -19,28 +19,18 @@ bumped.
 #### Ensure that all tests pass
 
 For major and minor releases we will be tagging the ``master`` branch.
-For patch releases, the ``stable`` branch.
-This should be as simple as verifying that the latest CI pipeline succeeded,
-however in ``stable`` branch also manually trigger CI task of building the
-conda package and verify that it, too, succeeds.
-
-
-#### Inspect the documentation
-
-If the CI pipeline succeeded, then the latest docs should be available at:
-
-    https://gitlab.kwant-project.org/qt/adaptive/pipelines
-
-Check that there are no glaring deficiencies.
+This should be as simple as verifying that the 
+[latest CI pipeline](https://gitlab.kwant-project.org/qt/adaptive/pipelines) 
+succeeded.
 
 
 #### Verify that `AUTHORS.md` is up-to-date
 
 The following command shows the number of commits per author since the last
-annotated tag::
-
-    t=$(git describe --abbrev=0); echo Commits since $t; git shortlog -s $t..
-
+annotated tag:
+```
+t=$(git describe --abbrev=0); echo Commits since $t; git shortlog -s $t..
+```
 
 ## Make a release, but do not publish it yet