Update How to release documentation

Change-Id: I02074836a000dcca2d5dc740370da3097497272b
Reviewed-on: https://review.couchbase.org/c/java-dcp-client/+/242197
Tested-by: Build Bot <build@couchbase.com>
Tested-by: <matthew.bray@couchbase.com>
Reviewed-by: <matthew.bray@couchbase.com>

Author: Couch-Matt

HOWTO-RELEASE.md

@@ -14,34 +14,13 @@ You will need:
   to a public keyserver. For bonus points, have a few co-workers sign your key.
 * To tell git about your signing key: `git config --global user.signingkey DEADBEEF`
   (replace `DEADBEEF` with the id of your PGP key).
-* A Sonatype account authorized to publish to the `com.couchbase` namespace.
-* A `~/.m2/settings.xml` file with a
-  [User Token](https://blog.sonatype.com/2012/08/securing-repository-credentials-with-nexus-pro-user-tokens/).
-  To generate a token, go to https://oss.sonatype.org and log in with your Sonatype account.
-  Click on your username (upper right) and select "Profile". From the drop-down menu,
-  select "User Token". Press "Access User Token" to see a snippet of XML with server credentials.
-  Copy and paste this XML into the `servers` section of your Maven settings,
-  replacing `${server}` with `ossrh`.
 * A local Docker installation, if you wish to run the integration tests.
 
-At a minimum, your `~/.m2/settings.xml` should look something like:
-
-    <settings>
-      <servers>
-        <server>
-          <id>central</id>
-          <username>xxxxxxxx</username>
-          <password>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</password>
-        </server>
-      </servers>
-    </settings>
-
-All set? In that case...
-
 ## Let's do this!
 
-Start by running `mvn clean verify -Prelease` to make sure the project builds successfully,
-artifact signing works, and the unit tests pass. To run the integration tests, run `mvn clean verify`
+Start by checking the snapshot builds found [here](https://github.com/couchbase/java-dcp-client/actions/workflows/deploy-snapshot.yml) to ensure that everything looks good with the current commit.
+
+To run the integration tests, run `mvn clean verify`
 without specifying a profile.
 When you're satisfied with the test results, it's time to...
 
@@ -50,42 +29,18 @@ When you're satisfied with the test results, it's time to...
 1. Edit `pom.xml` and remove the `-SNAPSHOT` suffix from the version string.
 2. Edit `examples/pom.xml` and update the `dcp.client.version` property to match the version string in Step 1.
 3. Commit these changes, with message "Prepare x.y.z release"
-   (where x.y.z is the version you're releasing).
+   (where x.y.z is the version you're releasing). Note: the snapshot build for that commit will fail because we removed the snapshot suffix. This is expected.
 
 ## Tag the release
 
 Run the command `git tag -s x.y.z` (where x.y.z is the release version number).
 
 Use the previous version's tag message (e.g. `git show 0.11.0`) as a template for
-the new version's tag message.
-
-Don't push the tag right away, though. Wait until the release is successful and you're sure
-there will be no more changes. Otherwise it can be a pain to remove an unwanted tag from Gerrit.
+the new version's tag message and then push the tag.
 
 ## Go! Go! Go!
 
-Make sure you don't have any uncommitted files in your workspace:
-
-    git status
-
-should say "nothing to commit, working tree clean".
-
-Here it is, the moment of truth. When you're ready to deploy to the Maven Central Repository:
-
-    ./mvnw clean deploy -Prelease
-
-Alternatively, if you prefer to inspect the staging repository and
-[complete the release manually](https://central.sonatype.org/pages/releasing-the-deployment.html),
-set this additional property:
-
-    ./mvnw clean deploy -Prelease -DautoReleaseAfterClose=false
-
-Whew, you did it! Or the build failed and you're looking at a cryptic error message, in which
-case you might want to check out the Troubleshooting section below.
-
-If the release succeeded, now's the time to publish the tag:
-
-    git push origin x.y.z
+Run the release workflow found [here](https://github.com/couchbase/java-dcp-client/actions/workflows/deploy-release.yml) supplying the tag name you previously pushed.
 
 ## Prepare for next dev cycle
 
@@ -94,12 +49,6 @@ Update the `dcp.client.version` property in `examples/pom.xml` to refer to the
 new snapshot version.
 Commit and push to Gerrit. Breathe in. Breathe out.
 
-## Publishing a snapshot
-
-After every passing nightly build, a snapshot should be published to the Sonatype OSS snapshot repository by running this command:
-
-    ./mvnw clean deploy -Psnapshot
-
 ## Troubleshooting
 
 * Take another look at the Prerequisites section. Did you miss anything?