[sling-site] branch master updated: linked the sling-tooling-release/update_reporter.sh script

[ra...@apache.org]

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

radu 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 9f5bff3  linked the sling-tooling-release/update_reporter.sh script
9f5bff3 is described below

commit 9f5bff311571adf8cbb7a436121897bd5af009f4
Author: Radu Cotescu <ra...@apache.org>
AuthorDate: Thu Jan 31 11:42:58 2019 +0100

    linked the sling-tooling-release/update_reporter.sh script
---
 src/main/jbake/content/documentation/development/release-management.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md
index 4e359b1..0b2a12d 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -214,6 +214,7 @@ If the vote passes:
         * Make sure to *not* change the end-of-line encoding of the .pom when uploaded via svn import! Eg when a windows style eol encoded file is uploaded with the setting '*.pom = svn:eol-style=native' this would later fail the signature checks!
         * Following the SVN commit you will receive an email from the 'Apache Reporter Service'. Follow the link and add the release data, as it used by the PMC chair to prepare board reports.
     1. Delete the old release artifacts from that same dist.apache.org svn folder (the dist directory is archived)
+    1. You will get an email from the Apache Reporter Service, which will ask you to add the information about the newly added release artifact. To simplify this task you can use the script from [https://github.com/apache/sling-tooling-release/blob/master/update_reporter.sh](https://github.com/apache/sling-tooling-release/blob/master/update_reporter.sh).
 1. Push the release to Maven Central
 	1. Login to [https://repository.apache.org](https://repository.apache.org) with your Apache SVN credentials. Click on *Staging*. Find your closed staging repository and select it by checking the select box. Select the *Releases* repository from the drop-down list and click *Release* from the menu above.
 	1. Once the release is promoted click on *Repositories*, select the *Releases* repository and validate that your artifacts are all there.