You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by st...@apache.org on 2016/09/26 11:31:41 UTC
svn commit: r1762317 -
/commons/cms-site/trunk/content/xdoc/releases/release.xml
Author: stain
Date: Mon Sep 26 11:31:40 2016
New Revision: 1762317
URL: http://svn.apache.org/viewvc?rev=1762317&view=rev
Log:
https links where appropriate (e.g. SVN)
Modified:
commons/cms-site/trunk/content/xdoc/releases/release.xml
Modified: commons/cms-site/trunk/content/xdoc/releases/release.xml
URL: http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/releases/release.xml?rev=1762317&r1=1762316&r2=1762317&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/releases/release.xml (original)
+++ commons/cms-site/trunk/content/xdoc/releases/release.xml Mon Sep 26 11:31:40 2016
@@ -118,12 +118,12 @@
</subsection>
<subsection name='3 Deploy Maven Artifacts'>
- <p>Login to the <a href="http://repository.apache.org">Nexus web interface</a>, select your staging
- repository and <a href="http://www.apache.org/dev/publishing-maven-artifacts.html#promote">promote</a>
+ <p>Login to the <a href="https://repository.apache.org">Nexus web interface</a>, select your staging
+ repository and <a 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 href="http://repo.maven.apache.org/maven2/">http://repo.maven.apache.org/maven2/</a>.
+ repository on <a href="https://repo.maven.apache.org/maven2/">https://repo.maven.apache.org/maven2/</a>.
</p>
</subsection>
@@ -159,7 +159,7 @@
<subsection name='5 Test Main Site Downloads'>
<p>
Wait until the release files are available from the main Apache web site
- (<code>http://www.apache.org/dist/commons/foo/</code>), then confirm things are good.
+ (<code>https://www.apache.org/dist/commons/foo/</code>), then confirm things are good.
</p>
<p>
Check the main directory:
@@ -214,7 +214,7 @@
<ol>
<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
the clirr report with the updated version info or update a local project with a dependency to the new
@@ -234,7 +234,7 @@
<subsection name="8 Update Main Website">
<ul>
- <li>Edit the file <a 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 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>
</ul>
@@ -250,8 +250,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