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 22d53b1  Automatic website deployment
22d53b1 is described below

commit 22d53b13499dc61e1fe7987365b8170fe56f4785
Author: jenkins <us...@infra.apache.org>
AuthorDate: Wed Jan 15 09:11:46 2020 +0000

    Automatic website deployment
---
 documentation/development/release-management.html | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/documentation/development/release-management.html 
b/documentation/development/release-management.html
index 28db499..38c7147 100644
--- a/documentation/development/release-management.html
+++ b/documentation/development/release-management.html
@@ -301,7 +301,7 @@ promote the artifacts to the central Maven repository.
 <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&#95;staged&#95;release.sh) and then simply copy t 
[...]
+      <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. See [#quick-update-of-artifacts-in-dist](the section on 
quick artifact updates) for a way to avoid having to checkout the whole folder 
first. The easiest to do this is to get the released artifact using the  [...]
         <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>
           <li>Following the SVN commit you will receive an email from the 
'Apache Reporter Service'. Follow the link and add the release data, as it used 
by the PMC chair to prepare board reports.</li>
@@ -322,6 +322,12 @@ promote the artifacts to the central Maven repository.
   <li>If you think that this release is worth a news entry, update the website 
at <a href="/news.html">news</a></li>
 </ol>
 <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" 
name="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>``` $ cd &lt;folder where 2.6.22 is found expanded source-release..zip&gt; 
$ svn import -m "Release org.apache.sling.engine-2.6.22" . 
https://dist.apache.org/repos/dist/release/sling</p>
+<p>$ 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) ```</p>
+<p>This makes sure that the new artifacts are imported and the old ones are 
deleted.</p>
 <h2><a href="#update-jira" name="update-jira">Update JIRA</a></h2>
 <p>Go to <a 
href="https://issues.apache.org/jira/plugins/servlet/project-config/SLING/versions";>Manage
 Versions</a> section on the SLING JIRA and mark the X.Y.Z version as released 
setting the release date to the date the vote has been closed.</p>
 <p>Also create a new version X.Y.Z+2, if that hasn't already been done.</p>
@@ -546,7 +552,7 @@ ssb   2048R/226BCE00 2016-01-21
             </div><footer class="footer">
                 <div class="content has-text-centered is-small">
 <div class="revisionInfo">
-                        Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Mon Jun 17 15:26:51 2019 +0200</span>
+                        Last modified by <span class="author">Robert 
Munteanu</span> on <span class="comment">Wed Jan 15 10:09:38 2020 +0100</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>

Reply via email to