You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by gi...@apache.org on 2021/08/31 10:36:36 UTC

[sling-site] branch asf-site updated: Automatic website deployment from https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/279/

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

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 48ac7b8  Automatic website deployment from https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/279/
48ac7b8 is described below

commit 48ac7b829c5d6188245519aba8fdef995149a2cc
Author: jenkins <bu...@apache.org>
AuthorDate: Tue Aug 31 10:36:34 2021 +0000

    Automatic website deployment from https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/279/
---
 documentation/development/release-management.html | 24 +----------------------
 sitemap.xml                                       |  4 ++--
 2 files changed, 3 insertions(+), 25 deletions(-)

diff --git a/documentation/development/release-management.html b/documentation/development/release-management.html
index 80527d1..8fe19a1 100644
--- a/documentation/development/release-management.html
+++ b/documentation/development/release-management.html
@@ -477,29 +477,7 @@ This majority vote is open for at least 72 hours
 <p>When gpg asks for e-mail linked the key you <em>MUST USE</em> the &lt;committer&gt;@apache.org one. When gpg asks for comment linked the key you <em>SHOULD USE</em> &quot;CODE SIGNING KEY&quot;</p>
 </li>
 <li>
-<p>You also have to add your public key either on <code>pool.sks-keyservers.net</code> or <code>pgp.mit.edu</code> (for the staging repository). To do so you can follow these steps:</p>
-<ol>
-<li>
-<p>Extract the key id from all the secret keys stored in the system:</p>
-<pre><code>$ gpg --list-secret-keys.
-</code></pre>
-<p>The output is something like this</p>
-<pre><code>gpg --list-secret-keys
-/Users/konradwindszus/.gnupg/secring.gpg
-----------------------------------------
-
-sec   2048R/455ECC7C 2016-01-21
-uid                  Konrad Windszus &lt;kwin@apache.org&gt;
-ssb   2048R/226BCE00 2016-01-21
-</code></pre>
-<p>The key id in this case is <code>455ECC7C</code>.</p>
-</li>
-<li>
-<p>Send the key towards e.g. <code>pool.sks-keyservers.net</code> via</p>
-<pre><code>$ gpg --keyserver pool.sks-keyservers.net --send-key &lt;key-id&gt;
-</code></pre>
-</li>
-</ol>
+<p>It's also good to upload your key to a public key server, see the [https://infra.apache.org/release-signing.html](ASF release signing page) for more info.</p>
 </li>
 <li>
 <p>Add the key to <a href="https://people.apache.org/keys/group/sling.asc">https://people.apache.org/keys/group/sling.asc</a></p>
diff --git a/sitemap.xml b/sitemap.xml
index 2d00cee..044a0c0 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -1,10 +1,10 @@
 <?xml version="1.0"?>
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd">
     <url>
-        <loc>https://sling.apache.org/releases.html</loc><lastmod>2021-08-30</lastmod>
-    </url><url>
         <loc>https://sling.apache.org/documentation/development/release-management.html</loc><lastmod>2021-08-31</lastmod>
     </url><url>
+        <loc>https://sling.apache.org/releases.html</loc><lastmod>2021-08-30</lastmod>
+    </url><url>
         <loc>https://sling.apache.org/documentation/bundles/repository-initialization.html</loc><lastmod>2021-08-25</lastmod>
     </url><url>
         <loc>https://sling.apache.org/documentation/bundles/scripting.html</loc><lastmod>2021-08-23</lastmod>