Author: buildbot
Date: Fri Mar 18 10:30:34 2016
New Revision: 983101
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 Fri Mar 18 10:30:34 2016
@@ -1 +1 @@
-1735281
+1735566
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
Fri Mar 18 10:30:34 2016
@@ -304,7 +304,7 @@ 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>Push the release to <a
href="https://dist.apache.org/repos/dist/release/";>https://dist.apache.org/repos/dist/release/</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>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>
</ul>
@@ -575,7 +575,7 @@ update your checkout and then publish th
</li>
</ol>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1734900 by rombert on Mon, 14 Mar 2016 09:12:00 +0000
+ Rev. 1735566 by radu on Fri, 18 Mar 2016 10:30:19 +0000
</div>
<div class="trademarkFooter">
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache
Sling project
