Author: buildbot
Date: Tue Sep 22 09:43:20 2015
New Revision: 966321
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 Tue Sep 22 09:43:20 2015
@@ -1 +1 @@
-1704493
+1704495
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
Tue Sep 22 09:43:20 2015
@@ -302,7 +302,10 @@ project to project, but the 'minimum of
<h2 id="promoting-the-release">Promoting the Release<a class="headerlink"
href="#promoting-the-release" title="Permanent link">¶</a></h2>
<p>If the vote passes:</p>
<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.*).</li>
+<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>
+</ul>
+</li>
<li>Delete the old release artifacts from that same dist.apache.org svn folder
(the dist directory is archived)</li>
<li>Login to <a
href="https://repository.apache.org";>https://repository.apache.org</a> with
your Apache SVN credentials. Click on <em>Staging</em>. Find your closed
staging repository and select it by checking the select box. Select the
<em>Releases</em> repository from the drop-down list and click <em>Release</em>
from the menu above.</li>
<li>Once the release is promoted click on <em>Repositories</em>, select the
<em>Releases</em> repository and validate that your artifacts are all
there.</li>
@@ -513,7 +516,7 @@ update your checkout and then publish th
</li>
</ol>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1693409 by rombert on Thu, 30 Jul 2015 11:04:43 +0000
+ Rev. 1704495 by stefanegli on Tue, 22 Sep 2015 09:43:04 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
