detail release process

Precise taglist.log and bundle.project location.
Mention the need of a working GPG environment.

Change-Id: Ie50fed9eb457af7cb1226e812852a7991bc4e0e1
Signed-off-by: guillaume.lambert <guillaume.lambert@orange.com>
(cherry picked from commit 8c89ab6b6881cea89a2b0190c445e42c78155bfa)

diff --git a/docs/release-process/project-release.rst b/docs/release-process/project-release.rst
index 04c0ba2637cb5fc56f8319bbf8b008d89ee9cc9c..90589143ead2eb08ac49d0cf24b5ab36722af05a 100644 (file)
--- a/docs/release-process/project-release.rst
+++ b/docs/release-process/project-release.rst
@@ -37,13 +37,15 @@ performed as follows:
 
 1. Ask helpdesk to sign the artifacts in staging repo
 2. Ask helpdesk to promote the staging repo
-3. Download taglist.log and project.bundle
+3. Download taglist.log and project.bundle files. They can be found in the
+   "patches" directory of the related jenkins release job logs.
 4. Read taglist.log and checkout the commit hash listed
 5. Merge the project.bundle patches
 6. Git tag the release
 7. Push release tag to Gerrit
 
 Steps 4-7 as bash:
+You will need a working GPG config to sign the release Git tag ("-s" option)
 
 .. code:: bash