Update release process instructions

Author: jozic

README.md

@@ -481,7 +481,28 @@ A new snapshot is deployed to sonatype on each commit merged to `main` branch. S
 
 ### New release deployment
 
-#### Prerequisites
+A new release can be done on demand using `Release new version` workflow. See [release.yml](.github/workflows/release.yml) for details.
+
+#### Steps
+1. [Run](https://github.com/scoverage/scoverage-maven-plugin/actions/workflows/release.yml) `Release new version` workflow.
+2. Wait ~ 8 hours for sync to maven central.
+3. Check jars are available in maven central https://search.maven.org/artifact/org.scoverage/scoverage-maven-plugin and GH label in README is updated.
+4. Checkout new tag, e.g. `git checkout scoverage-maven-plugin-2.1.2`.
+5. Generate site docs with `mvn clean site -P publicsite` and check that all required docs are generated in `./target/site`.
+6. Checkout `gh-pages` branch, e.g. `git checkout gh-pages`.
+7. Copy generated site to new directory named as version number, e.g. `cp -r ./target/site ./2.1.2`, commit and push.
+8. Wait several seconds for the docs to be published and verify, e.g. https://scoverage.github.io/scoverage-maven-plugin/2.1.2/check-mojo.html.
+9. Checkout `main` branch, e.g. `git checkout main`.
+10. Update versions in README, e.g. `sed -i 's/2.1.0/2.1.2/g' README.md`, commit and push.
+11. Create new Release on GitHub.
+
+
+This process will be fully or partially automated in the future.
+
+
+#### Releasing locally
+
+###### Prerequisites
 Set sonatype credentials in `~/.m2/settings.xml`:
 
 ```xml
@@ -497,24 +518,12 @@ Set sonatype credentials in `~/.m2/settings.xml`:
 ```
 Make sure you have proper pgp keys set up. See [Maven Central Guide](https://central.sonatype.org/pages/working-with-pgp-signatures.html) for details.
 
-#### Steps
+###### Steps
 
 1. Run
-`mvn -Darguments="-Dmaven.test.skip=true" -B release:clean release:prepare release:perform -P release`.
-2. Wait ~ 8 hours for sync to maven central.
-3. Check jars are available in maven central https://search.maven.org/artifact/org.scoverage/scoverage-maven-plugin and GH label in README is updated.
-4. Checkout new tag, e.g. `git checkout scoverage-maven-plugin-2.1.2`.
-5. Generate site docs with `mvn clean site -P publicsite` and check that all required docs are generated in `./target/site`.
-6. Checkout `gh-pages` branch, e.g. `git checkout gh-pages`.
-7. Copy generated site to new directory named as version number, e.g. `cp -r ./target/site ./2.1.2`, commit and push.
-8. Wait several seconds for the docs to be published and verify, e.g. https://scoverage.github.io/scoverage-maven-plugin/2.1.2/check-mojo.html.
-9. Checkout `main` branch, e.g. `git checkout main`.
-10. Update versions in README, e.g. `sed -i 's/2.1.0/2.1.2/g' README.md`, commit and push.
-11. Create new Release on GitHub.
-
+`mvn -ntp -B release:clean release:prepare release:perform -P release -Darguments="-DskipTests"`.
+2. Follow steps 2-11 above
 
-This process will be fully or partially automated in the future.
-
 ## License
 ```
 This software is licensed under the Apache 2 license, quoted below.