Author: buildbot
Date: Mon Aug 14 08:51:28 2017
New Revision: 1016770
Log:
Staging update by buildbot for sling
Modified:
websites/staging/sling/trunk/content/ (props changed)
websites/staging/sling/trunk/content/documentation/development/release-management.html
Propchange: websites/staging/sling/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Aug 14 08:51:28 2017
@@ -1 +1 @@
-1804956
+1804957
Modified:
websites/staging/sling/trunk/content/documentation/development/release-management.html
==============================================================================
---
websites/staging/sling/trunk/content/documentation/development/release-management.html
(original)
+++
websites/staging/sling/trunk/content/documentation/development/release-management.html
Mon Aug 14 08:51:28 2017
@@ -317,6 +317,7 @@ project to project, but the 'minimum of
<li>Push the release to <a
href="https://dist.apache.org/repos/dist/release/sling/";>https://dist.apache.org/repos/dist/release/sling/</a>.
This is only possible for PMC members (for a reasoning look at <a
href="http://www.apache.org/dev/release.html#upload-ci";>http://www.apache.org/dev/release.html#upload-ci</a>).
If you are not a PMC member, please ask one to do the upload for you.<ol>
<li>Commit the released artifacts to <a
href="https://dist.apache.org/repos/dist/release/sling/";>https://dist.apache.org/repos/dist/release/sling/</a>
which is replicated to <a
href="http://www.apache.org/dist/sling/";>http://www.apache.org/dist/sling/</a>
quickly via svnpubsub. Hint: use svn import to avoid having to checkout the
whole folder first. The easiest to do this is to get the released artifact
using the check script (check_staged_release.sh) and then simply copy
the artifacts from the downloaded folder to your local checkout folder. Make
sure to not add the checksum files for the signature file *.asc.*).<ul>
<li>Make sure to <em>not</em> 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!</li>
+<li>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.</li>
</ul>
</li>
<li>Delete the old release artifacts from that same dist.apache.org svn folder
(the dist directory is archived)</li>
@@ -634,7 +635,7 @@ to be updated.</p>
</ol>
<p>For background information about this process see the <a
href="http://maven.apache.org/developers/website/deploy-component-reference-documentation.html";>Maven
components reference documentation</a>.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1804956 by rombert on Mon, 14 Aug 2017 08:45:51 +0000
+ Rev. 1804957 by rombert on Mon, 14 Aug 2017 08:51:17 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
