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/06/10 07:08:43 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/182/
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 fb38702 Automatic website deployment from https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/182/
fb38702 is described below
commit fb3870288a7022fc8f1c2d7f51588712d3c1eae7
Author: jenkins <bu...@apache.org>
AuthorDate: Thu Jun 10 07:08:39 2021 +0000
Automatic website deployment from https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/182/
---
documentation/development/release-management.html | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/documentation/development/release-management.html b/documentation/development/release-management.html
index 5fd00ab..bb72a67 100644
--- a/documentation/development/release-management.html
+++ b/documentation/development/release-management.html
@@ -322,11 +322,10 @@ promote the artifacts to the central Maven repository.
<p>For the last two tasks, it's better to give the mirrors some time to distribute the uploaded artifacts (one day should be fine). This ensures that once the website (news and download page) is updated, people can actually download the artifacts.</p>
<h3><a href="#quick-update-of-artifacts-in-dist" id="quick-update-of-artifacts-in-dist">Quick update of artifacts in dist</a></h3>
<p>It is possible to update the artifacts without needing to checkout or update the full dist folder, which can be quite slow, by using <code>svn import</code> and <code>svn delete</code> on the remote SVN repository.</p>
-<p>Assuming that we are releasing <code>org.apache.sling.engine 2.6.22</code>, we can run the following commands</p>
+<p>Assuming that we are releasing <code>org.apache.sling.engine 2.6.22</code> and the old version artifact names start with <code>org.apache.sling.engine-2.6.20</code>, we can run the following commands</p>
<pre><code>$ cd <folder where 2.6.22 is found expanded source-release..zip>
$ svn import -m "Release org.apache.sling.engine-2.6.22" . https://dist.apache.org/repos/dist/release/sling
-
-$ svn delete -m "Release org.apache.sling.engine-2.6.22" $(ls | sed 's/22/20/' | while read line; do echo "https://dist.apache.org/repos/dist/release/sling/$line"; done)
+$ svn delete -m "Remove old version org.apache.sling.engine-2.6.20" $(svn ls https://dist.apache.org/repos/dist/release/sling/ | grep org.apache.sling.engine-2.6.20 | while read line; do echo "https://dist.apache.org/repos/dist/release/sling/$line"; done)
</code></pre>
<p>This makes sure that the new artifacts are imported and the old ones are deleted.</p>
<h2><a href="#update-jira" id="update-jira">Update JIRA</a></h2>
@@ -576,7 +575,7 @@ $ svn up KEYS
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Stefan Egli</span> on <span class="comment">Mon Apr 19 15:48:09 2021 +0200</span>
+ Last modified by <span class="author">Konrad Windszus</span> on <span class="comment">Thu Jun 10 09:05:05 2021 +0200</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</p><p>