[sling-site] branch master updated: add paragraph "Redoing release perform"

[ol...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

olli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new fcd6be8  add paragraph "Redoing release perform"
fcd6be8 is described below

commit fcd6be8ef0f1ac80b0929fad50dadc5afab35a19
Author: Oliver Lietz <ol...@apache.org>
AuthorDate: Sat Sep 22 12:37:02 2018 +0200

    add paragraph "Redoing release perform"
---
 .../documentation/development/release-management.md       | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md
index dc95a14..3760fbb 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -92,9 +92,22 @@ First prepare your POMs for release:
     * Login to [https://repository.apache.org](https://repository.apache.org) using your Apache credentials. Click on *Staging* on the left. Then click on *org.apache.sling* in the list of repositories. In the panel below you should see an open repository that is linked to your username and IP. Right click on this repository and select *Close*. This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, s [...]
 
 1. Verify the staged artifacts
-    * If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of \*.asc (signature) files. If you don't like the content of the repository, right click your repository and choose *Drop*. You can then rollback your release (see *Canceling the Release*) and repeat the process
+    * If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of \*.asc (signature) files. If you don't like the content of the repository, right click your repository and choose *Drop*. You can then redo (see [Redoing release perform](#redoing-release-perform)) or rollback your release (see *Canceling the Release*) and repeat the process
     * Note the staging repository URL, especially the number at the end of the URL. You will need this in your vote email
 
+### Redoing release perform
+
+If perform fails for whatever reason (e.g. staged artifacts are incomplete or signed with a wrong key) drop the staging repository and create a required `release.properties` file containing `scm.url` and `scm.tag` manually.
+
+Example `release.properties` file:
+
+    scm.url=scm:git:https://gitbox.apache.org/repos/asf/sling-org-apache-sling-settings.git
+    scm.tag=org.apache.sling.settings-1.3.10
+
+Execute perform step again:
+
+    $ mvn release:perform
+
 ### Redeploying staged artifacts
 
 It may happen that deployment to Nexus fails or is partially successful. To fix such a deployment, you can re-deploy the artifacts from within the SCM checkout: