Document release procedure in README

Added release procedure instructions including GPG setup and Maven commands.

Author: jmesnil

README.md

@@ -36,4 +36,49 @@ The versions of all dependencies and plugins that are used by this archetype are
 For each archetype, their archetype-resources `pom.xml` is still in Git but in a separate source tree (e.g. `wildfly-jakartaee-ear-archetype/src/main/resources-filtered/archetype-resources/pom.xml`).
 When the archetypes are built, their `pom.xml` are filtered with the property values from the parent pom (so their own `version.wildfly.bom` will have the *actual* value of the parent's `version.wildfly.bom`).
 
-The reason of this structure is that we want to evaluate some property values when we built the archetype (for the versions) and keep others that will be evaluate when the project is generated by the archetypes (eg `${rootArtifactId}`) . The latter properties are escaped from filtering by prepending a `\`.
+The reason of this structure is that we want to evaluate some property values when we built the archetype (for the versions) and keep others that will be evaluate when the project is generated by the archetypes (eg `${rootArtifactId}`) . The latter properties are escaped from filtering by prepending a `\`.
+
+## Release Procedure
+
+Prior to releasing you should ensure you have your own GPG signing key set up, published to a key server and listed on [wildfly.org](https://www.wildfly.org/contributors/pgp/).
+
+### Prepare the release
+
+Execute:
+
+```
+mvn release:prepare -Pjboss-release
+```
+
+### Perform the release
+
+Execute:
+
+```
+mvn release:perform -Pjboss-release
+```
+
+This will deploy the release to the `wildfly-staging` repository.
+
+Wait for 10 minutes then visit the Validation task for the [`wildfly-staging` repository in Nexus](https://repository.jboss.org/nexus/#browse/browse:wildfly-staging). If this task ran at least 10 minutes after the release was deployed check the latest results on the Settings tab and verify that at least one component was processed and that there were no errors. If the task has not run it can be manually kicked off using the Run button.
+
+e.g.
+
+> Processed X components.
+> - no errors were found.
+> - the deployment was a dry run (no actual publishing).
+
+If others are also deploying at the same time this count could be higher, the important check is that the scan was at least 10 minutes after it was deployed, 1 or more components were scanned and no errors specific to Remoting JMX are reported.
+
+### Complete the release
+
+If no issues are reported complete the release.
+
+Move the component to the releases repository:
+
+```
+git checkout <tag of the release>
+mvn nxrm3:staging-move
+```
+
+Once this is done, the release will be pushed to the `releases` repository in Nexus and then to Maven Central.