subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From julianf...@apache.org
Subject svn commit: r934387 - /subversion/site/publish/roadmap.html
Date Thu, 15 Apr 2010 12:28:24 GMT
Author: julianfoad
Date: Thu Apr 15 12:28:24 2010
New Revision: 934387

URL: http://svn.apache.org/viewvc?rev=934387&view=rev
Log:
* roadmap.html: Fix some broken links, and delete some others.

Suggested by: Jon Foster <Jon.Foster{_AT_}cabot.co.uk>.

Modified:
    subversion/site/publish/roadmap.html

Modified: subversion/site/publish/roadmap.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/roadmap.html?rev=934387&r1=934386&r2=934387&view=diff
==============================================================================
--- subversion/site/publish/roadmap.html (original)
+++ subversion/site/publish/roadmap.html Thu Apr 15 12:28:24 2010
@@ -57,7 +57,8 @@ the typical nomination/review/vote/merge
 to the release, and it also allows some time for committers to test and sign
 the tarball before the weekend hits.  The release is finalized and announced
 shortly after all the signatures are collected.  See the
-<a href="release-process.html">release process</a> for more information.</p>
+<a href="/docs/community-guide/releasing.html">release process</a> for more
+information.</p>
 
 </div>
 
@@ -91,7 +92,7 @@ Subversion 2.0, will probably be done mu
 just with more planning around the exact features.  For more
 information about Subversion's release numbering and compatibility
 policies, see the section entitled
-<a href="/docs/community-guide/#release-numbering" >"Release
+<a href="/docs/community-guide/releasing.html#release-numbering" >"Release
 numbering, compatibility, and deprecation"</a> in the
 <a href="/docs/community-guide/">Subversion Community Guide</a>.</p>
 
@@ -125,8 +126,8 @@ we can express dependencies and predict 
 be worked on.  <em>Just because a feature is listed for a particular
 release does not guarantee that it will be in that release.</em>  Hard
 feature lists don't actually get set until the <a
-href="release-process.html#release-branches">release branch</a> is
-created.  The best way to track development is to <a
+href="/docs/community-guide/releasing.html#release-branches">release
+branch</a> is created.  The best way to track development is to <a
 href="mailing-lists.html">subscribe</a> to the
 development mailing list, <a href="mailto:dev@subversion.apache.org"
 >dev@subversion.apache.org</a>.</p>
@@ -159,14 +160,11 @@ development mailing list, <a href="mailt
         href="http://subversion.tigris.org/issues/show_bug.cgi?id=898"
         >issue #898</a>)</li>
 
-        <li>Log message templates  (see <a href="http://subversion.tigris.org/servlets/BrowseList?list=dev&amp;by=thread&amp;from=325870"
-        >discussion thread</a>)</li>
+        <li>Log message templates</li>
 
-        <li>Repository-defined autoprops (see <a href="http://subversion.tigris.org/servlets/BrowseList?list=dev&amp;by=thread&amp;from=329707"
-        >discussion thread</a>)</li>
+        <li>Repository-defined autoprops</li>
 
-        <li>Inherited properties (see <a href="http://subversion.tigris.org/servlets/BrowseList?list=dev&amp;by=thread&amp;from=326933"
-        >discussion thread</a>)</li>
+        <li>Inherited properties</li>
       </ul>
     </li>
   </ul>



Mime
View raw message