You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by se...@apache.org on 2011/10/13 03:00:53 UTC

svn commit: r1182628 - /commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml

Author: sebb
Date: Thu Oct 13 01:00:53 2011
New Revision: 1182628

URL: http://svn.apache.org/viewvc?rev=1182628&view=rev
Log:
Don't use symbolic links any more

Modified:
    commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml

Modified: commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml?rev=1182628&r1=1182627&r2=1182628&view=diff
==============================================================================
--- commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml (original)
+++ commons/proper/commons-site/trunk/src/site/xdoc/releases/release.xml Thu Oct 13 01:00:53 2011
@@ -102,24 +102,9 @@
     gives instructions on how to do this.
     </p>
     <p>
-    <strong>Update Symbolic Links</strong><br/>
-    Remove symbolic links to current distributions
-    <pre>
-      rm commons-foo-current* </pre>
-    </p>
-    <p>
-    Recreate links to current distribution:
-    </p>
-    <p>
-    From committers/tools/releases in the ASF subversion repository, download the script
-    "symlinks.sh" and install it in your home/bin directory.  Make sure it is executable
-    and your path includes your /bin subdirectory.  From the top level distribution directory
-    (/www/www.apache.org/dist/commons/foo/), execute
-    <pre>
-      symlinks.sh 1.2</pre>
-    </p>
-    <p>Please test that these links function correctly!</p>
-    <p>
+    <strong>Symbolic Links</strong><br/>
+    These are no longer to be used, so please
+    <a href="http://www.apache.org/dev/mirror-step-by-step.html#symbolic_links">do not use symbolic links in mirrored directories!</a>
     <strong>Update RELEASE-NOTES</strong><br/>
     Replace the current <code>RELEASE-NOTES.txt</code> with the new release notes.
     <pre>