svn commit: r982563 - in /websites/staging/sling/trunk/content: ./ documentation/development/release-management.html

[bu...@apache.org]

Author: buildbot
Date: Sat Mar 12 10:37:38 2016
New Revision: 982563

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 Sat Mar 12 10:37:38 2016
@@ -1 +1 @@
-1734680
+1734683

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 Sat Mar 12 10:37:38 2016
@@ -304,13 +304,19 @@ 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">&para;</a></h2>
 <p>If the vote passes:</p>
 <ol>
+<li>Upload 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>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&#95;staged&#95;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>
+</ol>
+</li>
+<li>Upload the release to Maven Central<ol>
 <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>
+</ol>
+</li>
 <li>If you're releasing bundles, you should also add them to the Sling Release OBR (see <em>Appendix C</em>).</li>
 <li>Update the news section on the website at <a href="/news.html">news</a>.</li>
 <li>Update the download page on the website at <a href="/downloads.cgi">downloads</a> to point to the new release.</li>
@@ -567,7 +573,7 @@ update your checkout and then publish th
 </li>
 </ol>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1726023 by kwin on Thu, 21 Jan 2016 17:00:58 +0000
+        Rev. 1734683 by kwin on Sat, 12 Mar 2016 10:37:24 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project