commons-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r998290 - in /websites/staging/commons/trunk/content: ./ releases/release.html
Date Mon, 26 Sep 2016 11:31:53 GMT
Author: buildbot
Date: Mon Sep 26 11:31:53 2016
New Revision: 998290

Log:
Staging update by buildbot for commons

Modified:
    websites/staging/commons/trunk/content/   (props changed)
    websites/staging/commons/trunk/content/releases/release.html

Propchange: websites/staging/commons/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Sep 26 11:31:53 2016
@@ -1 +1 @@
-1762316
+1762317

Modified: websites/staging/commons/trunk/content/releases/release.html
==============================================================================
--- websites/staging/commons/trunk/content/releases/release.html (original)
+++ websites/staging/commons/trunk/content/releases/release.html Mon Sep 26 11:31:53 2016
@@ -341,13 +341,13 @@
 <div class="section">
 <h3><a name="a3_Deploy_Maven_Artifacts"></a>3 Deploy Maven Artifacts</h3>
     
-<p>Login to the <a class="externalLink" href="http://repository.apache.org">Nexus
web interface</a>, select your staging
-      repository and <a class="externalLink" href="http://www.apache.org/dev/publishing-maven-artifacts.html#promote">promote</a>
+<p>Login to the <a class="externalLink" href="https://repository.apache.org">Nexus
web interface</a>, select your staging
+      repository and <a class="externalLink" href="https://www.apache.org/dev/publishing-maven-artifacts.html#promote">promote</a>
       it.</p>
     
 <p>
     The files placed here will be mirrored (after some delay) to the public distribution
-    repository on <a class="externalLink" href="http://repo.maven.apache.org/maven2/">http://repo.maven.apache.org/maven2/</a>.
+    repository on <a class="externalLink" href="https://repo.maven.apache.org/maven2/">https://repo.maven.apache.org/maven2/</a>.
     </p>
   </div>
 
@@ -397,7 +397,7 @@
     
 <p>
     Wait until the release files are available from the main Apache web site
-    (<tt>http://www.apache.org/dist/commons/foo/</tt>), then confirm things are
good.
+    (<tt>https://www.apache.org/dist/commons/foo/</tt>), then confirm things
are good.
     </p>
     
 <p>
@@ -472,7 +472,7 @@
 <li>The release artifacts are available on the mirrors.</li>
     
 <li>The component website including the updated download page has been updated on the
public site
-      http://commons.apache.org/proper/foo.</li>
+      https://commons.apache.org/proper/foo.</li>
     
 <li>If the component publishes maven artifacts, these artifacts have been replicated
to the central
         maven repo at repo.maven.apache.org. (Clear your local repo of the release artifacts
and either activate
@@ -502,7 +502,7 @@
     
 <ul>
       
-<li>Edit the file <a class="externalLink" href="http://svn.apache.org/repos/asf/commons/cms-site/trunk/conf/component_releases.properties">http://svn.apache.org/repos/asf/commons/cms-site/trunk/conf/component_releases.properties</a>
+<li>Edit the file <a class="externalLink" href="https://svn.apache.org/repos/asf/commons/cms-site/trunk/conf/component_releases.properties">https://svn.apache.org/repos/asf/commons/cms-site/trunk/conf/component_releases.properties</a>
         to hold the current version and release date for your compontent.  This can be done
using the CMS.</li>
       
 <li><a href="../site-publish.html#Main_site">Stage and publish</a> the
main website using the CMS.</li>
@@ -524,8 +524,8 @@
     Unless old versions are especially required, remove them from the dist directory. This
     will cause the files to also be deleted from the mirrors and
     save them some diskspace as well as simplifying things for users.
-      Note that the contents of the http://www.apache.org/dist directory is regularly copied
to
-      http://archive.apache.org/dist.
+      Note that the contents of the https://www.apache.org/dist directory is regularly copied
to
+      https://archive.apache.org/dist.
     Deleting files from the standard distribution directories
       on https://dist.apache.org/repos/dist/release/commons/ does <i>not</i>
delete
     them from the archive dist directories so users will



Mime
View raw message