docs: update and move the release docs

Author: Abbe98

README.md

@@ -90,11 +90,4 @@ To avoid having to unzip the extension in the corresponding directory every time
 
 ### Releasing it
 
-- Make sure you are on the `master` branch and it is up to date (`git pull`)
-- Open `pom.xml` and set the version to the desired version number, such as `<version>0.1.0</version>`
-- Commit and push those changes to master
-- Add a corresponding git tag, with `git tag -a v0.1.0 -m "Version 0.1.0"` (when working from GitHub Desktop, you can follow [this process](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/managing-commits/managing-tags) and manually add the `v0.1.0` tag with the description `Version 0.1.0`)
-- Push the tag to GitHub: `git push --tags` (in GitHub Desktop, just push again)
-- Create a new release on GitHub at https://github.com/OpenRefine/CommonsExtension/releases/new, providing a release title (such as "Commons extension 0.1.0") and a description of the features in this release.
-- Open `pom.xml` and set the version to the expected next version number, followed by `-SNAPSHOT`. For instance, if you just released 0.1.0, you could set `<version>0.1.1-SNAPSHOT</version>`
-- Commit and push those changes.
+See [RELEASE.md](RELEASE.md).

RELEASE.md

@@ -0,0 +1,7 @@
+# Releasing CommonsExtension
+
+1. Make sure you are on the `master` branch and it is up to date (`git pull`)
+2. Open `pom.xml` and set the version to the desired version number, such as `<version>0.1.0</version>`
+3. Commit and push those changes to master
+4. Create a new release on GitHub at https://github.com/OpenRefine/CommonsExtension/releases/new, providing a release title (such as "Commons extension 0.1.0") and a description of the features in this release. You can copy the content of the last release go get a starting template. Also create a new tag following the existing pattern.
+