You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by cm...@apache.org on 2010/07/23 18:24:35 UTC
svn commit: r967156 - /subversion/site/publish/docs/community-guide/
Author: cmpilato
Date: Fri Jul 23 16:24:34 2010
New Revision: 967156
URL: http://svn.apache.org/viewvc?rev=967156&view=rev
Log:
Fix the Community Guide's internal links so that when in single-page
viewing mode internal links point to single-page destinations, and
when viewing the Guide in parts the internal links point to the
correct individual part.
* site/publish/docs/community-guide/building.html,
* site/publish/docs/community-guide/conventions.html,
* site/publish/docs/community-guide/debugging.html,
* site/publish/docs/community-guide/general.html,
* site/publish/docs/community-guide/issues.html,
* site/publish/docs/community-guide/l10n.html,
* site/publish/docs/community-guide/mailing-lists.html,
* site/publish/docs/community-guide/building.part.html,
* site/publish/docs/community-guide/releasing.html,
* site/publish/docs/community-guide/roles.html
Use SSI #set to set a bunch of page name definition variables here
for the names of the pieces of this Community Guide.
* site/publish/docs/community-guide/conventions.part.html,
* site/publish/docs/community-guide/debugging.part.html,
* site/publish/docs/community-guide/general.part.html,
* site/publish/docs/community-guide/issues.part.html,
* site/publish/docs/community-guide/l10n.part.html,
* site/publish/docs/community-guide/mailing-lists.part.html,
* site/publish/docs/community-guide/releasing.part.html,
* site/publish/docs/community-guide/roles.part.html
Replace explicit or implicit references to individual pages in this
Community Guide with SSI #echo statements for page name variables.
* site/publish/docs/community-guide/community-guide.html
Set the page name definition variables to the empty string. This
allows all "intra-page" bookmarks to still point to the single-page
layout of the Community Guide.
Reported by: gstein
Modified:
subversion/site/publish/docs/community-guide/building.html
subversion/site/publish/docs/community-guide/building.part.html
subversion/site/publish/docs/community-guide/community-guide.html
subversion/site/publish/docs/community-guide/conventions.html
subversion/site/publish/docs/community-guide/conventions.part.html
subversion/site/publish/docs/community-guide/debugging.html
subversion/site/publish/docs/community-guide/debugging.part.html
subversion/site/publish/docs/community-guide/general.html
subversion/site/publish/docs/community-guide/general.part.html
subversion/site/publish/docs/community-guide/issues.html
subversion/site/publish/docs/community-guide/issues.part.html
subversion/site/publish/docs/community-guide/l10n.html
subversion/site/publish/docs/community-guide/l10n.part.html
subversion/site/publish/docs/community-guide/mailing-lists.html
subversion/site/publish/docs/community-guide/mailing-lists.part.html
subversion/site/publish/docs/community-guide/releasing.html
subversion/site/publish/docs/community-guide/releasing.part.html
subversion/site/publish/docs/community-guide/roles.html
subversion/site/publish/docs/community-guide/roles.part.html
Modified: subversion/site/publish/docs/community-guide/building.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/building.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/building.html (original)
+++ subversion/site/publish/docs/community-guide/building.html Fri Jul 23 16:24:34 2010
@@ -15,6 +15,16 @@
<div id="site-content">
<!--#include virtual="/site-notice.html" -->
+<!--#set var="GUIDE_BUILDING_PAGE" value="building.html" -->
+<!--#set var="GUIDE_CONVENTIONS_PAGE" value="conventions.html" -->
+<!--#set var="GUIDE_DEBUGGING_PAGE" value="debugging.html" -->
+<!--#set var="GUIDE_GENERAL_PAGE" value="general.html" -->
+<!--#set var="GUIDE_ISSUES_PAGE" value="issues.html" -->
+<!--#set var="GUIDE_L10N_PAGE" value="l10n.html" -->
+<!--#set var="GUIDE_MAILINGLISTS_PAGE" value="mailing-lists.html" -->
+<!--#set var="GUIDE_RELEASING_PAGE" value="releasing.html" -->
+<!--#set var="GUIDE_ROLES_PAGE" value="roles.html" -->
+
<!--#include virtual="guide-nav.html" -->
<!--#include virtual="building.part.html" -->
Modified: subversion/site/publish/docs/community-guide/building.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/building.part.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/building.part.html (original)
+++ subversion/site/publish/docs/community-guide/building.part.html Fri Jul 23 16:24:34 2010
@@ -1,6 +1,6 @@
<div class="h1" id="building-and-testing">
<h1>Building and Testing
- <a class="sectionlink" href="#building-and-testing"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_BUILDING_PAGE" -->#building-and-testing"
title="Link to this section">¶</a>
</h1>
@@ -8,7 +8,7 @@
<div class="h2" id="configury">
<h2>The configuration/build system under unix
- <a class="sectionlink" href="#configury"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_BUILDING_PAGE" -->#configury"
title="Link to this section">¶</a>
</h2>
@@ -227,7 +227,7 @@ it again.</p>
<div class="h2" id="automated-tests">
<h2>Automated tests
- <a class="sectionlink" href="#automated-tests"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_BUILDING_PAGE" -->#automated-tests"
title="Link to this section">¶</a>
</h2>
@@ -254,7 +254,7 @@ href="http://svn.apache.org/repos/asf/su
<div class="h2" id="build-farm">
<h2>Build farm
- <a class="sectionlink" href="#build-farm"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_BUILDING_PAGE" -->#build-farm"
title="Link to this section">¶</a>
</h2>
@@ -289,7 +289,7 @@ can serve as a good starting point?</p>
<div class="h2" id="write-test-cases-first">
<h2>Writing test cases before code
- <a class="sectionlink" href="#write-test-cases-first"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_BUILDING_PAGE" -->#write-test-cases-first"
title="Link to this section">¶</a>
</h2>
Modified: subversion/site/publish/docs/community-guide/community-guide.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/community-guide.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/community-guide.html (original)
+++ subversion/site/publish/docs/community-guide/community-guide.html Fri Jul 23 16:24:34 2010
@@ -15,6 +15,16 @@
<div id="site-content">
<!--#include virtual="/site-notice.html" -->
+<!--#set var="GUIDE_BUILDING_PAGE" value="" -->
+<!--#set var="GUIDE_CONVENTIONS_PAGE" value="" -->
+<!--#set var="GUIDE_DEBUGGING_PAGE" value="" -->
+<!--#set var="GUIDE_GENERAL_PAGE" value="" -->
+<!--#set var="GUIDE_ISSUES_PAGE" value="" -->
+<!--#set var="GUIDE_L10N_PAGE" value="" -->
+<!--#set var="GUIDE_MAILINGLISTS_PAGE" value="" -->
+<!--#set var="GUIDE_RELEASING_PAGE" value="" -->
+<!--#set var="GUIDE_ROLES_PAGE" value="" -->
+
<h1>Subversion Community Guide (aka "HACKING")</h1>
<p>If you are contributing to the Subversion project, please read this
Modified: subversion/site/publish/docs/community-guide/conventions.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/conventions.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/conventions.html (original)
+++ subversion/site/publish/docs/community-guide/conventions.html Fri Jul 23 16:24:34 2010
@@ -15,6 +15,16 @@
<div id="site-content">
<!--#include virtual="/site-notice.html" -->
+<!--#set var="GUIDE_BUILDING_PAGE" value="building.html" -->
+<!--#set var="GUIDE_CONVENTIONS_PAGE" value="conventions.html" -->
+<!--#set var="GUIDE_DEBUGGING_PAGE" value="debugging.html" -->
+<!--#set var="GUIDE_GENERAL_PAGE" value="general.html" -->
+<!--#set var="GUIDE_ISSUES_PAGE" value="issues.html" -->
+<!--#set var="GUIDE_L10N_PAGE" value="l10n.html" -->
+<!--#set var="GUIDE_MAILINGLISTS_PAGE" value="mailing-lists.html" -->
+<!--#set var="GUIDE_RELEASING_PAGE" value="releasing.html" -->
+<!--#set var="GUIDE_ROLES_PAGE" value="roles.html" -->
+
<!--#include virtual="guide-nav.html" -->
<!--#include virtual="conventions.part.html" -->
Modified: subversion/site/publish/docs/community-guide/conventions.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/conventions.part.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/conventions.part.html (original)
+++ subversion/site/publish/docs/community-guide/conventions.part.html Fri Jul 23 16:24:34 2010
@@ -1,6 +1,6 @@
<div class="h1" id="conventions">
<h1>Coding and Commit Conventions
- <a class="sectionlink" href="#conventions"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#conventions"
title="Link to this section">¶</a>
</h1>
@@ -8,7 +8,7 @@
<div class="h2" id="interface-visibility">
<h2>Code modularity and interface visibility
- <a class="sectionlink" href="#interface-visibility"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#interface-visibility"
title="Link to this section">¶</a>
</h2>
@@ -53,7 +53,7 @@ files in <tt>subversion/include/private/
<div class="h2" id="coding-style">
<h2>Coding style
- <a class="sectionlink" href="#coding-style"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#coding-style"
title="Link to this section">¶</a>
</h2>
@@ -101,7 +101,7 @@ extra line on the screen.</p>
<div class="h2" id="use-page-breaks">
<h2>Using page breaks
- <a class="sectionlink" href="#use-page-breaks"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#use-page-breaks"
title="Link to this section">¶</a>
</h2>
@@ -120,7 +120,7 @@ as you might think, and if you'd like to
<div class="h2" id="error-messages">
<h2>Error message conventions
- <a class="sectionlink" href="#error-messages"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#error-messages"
title="Link to this section">¶</a>
</h2>
@@ -181,14 +181,14 @@ as you might think, and if you'd like to
</ul>
-<p>Also read about <a href="#l10n">Localization</a>.</p>
+<p>Also read about <a href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#l10n">Localization</a>.</p>
</div> <!-- error-messages -->
<div class="h2" id="apr-pools">
<h2>APR pool usage conventions
- <a class="sectionlink" href="#apr-pools"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#apr-pools"
title="Link to this section">¶</a>
</h2>
@@ -322,7 +322,7 @@ should not have a `pool' field. Just al
you need in the current pool — when that pool gets
cleared or destroyed, they will all go away simultaneously.</p>
-<p>See also the <a href="#exception-handling">Exception handling</a>
+<p>See also the <a href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#exception-handling">Exception handling</a>
section, for details of how resources associated with a pool are
cleaned up when that pool is destroyed.</p>
@@ -365,7 +365,7 @@ cleaned up when that pool is destroyed.<
</ul>
-<p>See also <a href="#tracing-memory-leaks">Tracking down memory
+<p>See also <a href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#tracing-memory-leaks">Tracking down memory
leaks</a> for tips on diagnosing pool usage problems.</p>
</div> <!-- apr-pools -->
@@ -373,7 +373,7 @@ leaks</a> for tips on diagnosing pool us
<div class="h2" id="apr-status-codes">
<h2>APR status codes
- <a class="sectionlink" href="#apr-status-codes"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#apr-status-codes"
title="Link to this section">¶</a>
</h2>
@@ -386,7 +386,7 @@ for portability to non-Unix platforms.</
<div class="h2" id="exception-handling">
<h2>Exception handling
- <a class="sectionlink" href="#exception-handling"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#exception-handling"
title="Link to this section">¶</a>
</h2>
@@ -421,7 +421,7 @@ return svn_error_create(SVN_ERR_FOO, NUL
<p>NOTICE the NULL field... indicating that this error has no
child, i.e. it is the bottom-most error.</p>
- <p>See also the <a href="#error-messages"> section on writing
+ <p>See also the <a href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#error-messages"> section on writing
error messages</a>.</p>
<p>Subversion internally uses UTF-8 to store its data. This also
@@ -557,7 +557,7 @@ return svn_error_create(SVN_ERR_FOO, NUL
<div class="h2" id="secure-coding">
<h2>Secure coding guidelines
- <a class="sectionlink" href="#secure-coding"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#secure-coding"
title="Link to this section">¶</a>
</h2>
@@ -613,7 +613,7 @@ risk of exposure.</p>
<div class="h2" id="destruction-of-stacked-resources">
<h2>Destruction of stacked resources
- <a class="sectionlink" href="#destruction-of-stacked-resources"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#destruction-of-stacked-resources"
title="Link to this section">¶</a>
</h2>
@@ -677,7 +677,7 @@ to do so.</p>
<div class="h2" id="other-conventions">
<h2>Other coding conventions
- <a class="sectionlink" href="#other-conventions"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#other-conventions"
title="Link to this section">¶</a>
</h2>
@@ -746,7 +746,7 @@ conventions:</p>
outside of a library were put into public header files,
using the double underscore notation. This practice has been
abandoned, and any such symbols are legacy, maintained for <a
- href="#release-numbering">backwards compatibility</a>.</p>
+ href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#release-numbering">backwards compatibility</a>.</p>
</li>
<li><p>In text strings that might be printed out (or otherwise made
@@ -831,7 +831,7 @@ conventions:</p>
<div class="h2" id="log-messages">
<h2>Writing log messages
- <a class="sectionlink" href="#log-messages"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#log-messages"
title="Link to this section">¶</a>
</h2>
@@ -973,7 +973,7 @@ of changes that accomplishes a single go
start with a sentence or two summarizing the change. Truly
independent changes should be made in separate commits, of course.</p>
-<p>See <a href="#crediting">Crediting</a> for how to give credit to
+<p>See <a href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#crediting">Crediting</a> for how to give credit to
someone else if you are committing their patch, or committing a change
they suggested.</p>
@@ -1037,7 +1037,7 @@ made.</p>
<div class="h2" id="crediting">
<h2>Crediting
- <a class="sectionlink" href="#crediting"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_CONVENTIONS_PAGE" -->#crediting"
title="Link to this section">¶</a>
</h2>
Modified: subversion/site/publish/docs/community-guide/debugging.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/debugging.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/debugging.html (original)
+++ subversion/site/publish/docs/community-guide/debugging.html Fri Jul 23 16:24:34 2010
@@ -15,6 +15,16 @@
<div id="site-content">
<!--#include virtual="/site-notice.html" -->
+<!--#set var="GUIDE_BUILDING_PAGE" value="building.html" -->
+<!--#set var="GUIDE_CONVENTIONS_PAGE" value="conventions.html" -->
+<!--#set var="GUIDE_DEBUGGING_PAGE" value="debugging.html" -->
+<!--#set var="GUIDE_GENERAL_PAGE" value="general.html" -->
+<!--#set var="GUIDE_ISSUES_PAGE" value="issues.html" -->
+<!--#set var="GUIDE_L10N_PAGE" value="l10n.html" -->
+<!--#set var="GUIDE_MAILINGLISTS_PAGE" value="mailing-lists.html" -->
+<!--#set var="GUIDE_RELEASING_PAGE" value="releasing.html" -->
+<!--#set var="GUIDE_ROLES_PAGE" value="roles.html" -->
+
<!--#include virtual="guide-nav.html" -->
<!--#include virtual="debugging.part.html" -->
Modified: subversion/site/publish/docs/community-guide/debugging.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/debugging.part.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/debugging.part.html (original)
+++ subversion/site/publish/docs/community-guide/debugging.part.html Fri Jul 23 16:24:34 2010
@@ -1,6 +1,6 @@
<div class="h1" id="debugging">
<h1>Debugging Subversion
- <a class="sectionlink" href="#debugging"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_DEBUGGING_PAGE" -->#debugging"
title="Link to this section">¶</a>
</h1>
@@ -8,13 +8,13 @@
<div class="h2" id="server-debugging">
<h2>Debugging the server
- <a class="sectionlink" href="#server-debugging"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_DEBUGGING_PAGE" -->#server-debugging"
title="Link to this section">¶</a>
</h2>
<div class="h3" id="debugging-ra-dav">
<h3>Debugging the DAV server
- <a class="sectionlink" href="#debugging-ra-dav"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_DEBUGGING_PAGE" -->#debugging-ra-dav"
title="Link to this section">¶</a>
</h3>
@@ -52,7 +52,7 @@ breakpoints.</p>
<div class="h3" id="debugging-ra-svn">
<h3>Debugging the ra_svn client and server, on Unix
- <a class="sectionlink" href="#debugging-ra-svn"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_DEBUGGING_PAGE" -->#debugging-ra-svn"
title="Link to this section">¶</a>
</h3>
@@ -137,7 +137,7 @@ server, "set x = 0", and step through th
<div class="h2" id="net-trace">
<h2>Tracing network traffic
- <a class="sectionlink" href="#net-trace"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_DEBUGGING_PAGE" -->#net-trace"
title="Link to this section">¶</a>
</h2>
@@ -220,7 +220,7 @@ with < and > signs to show the dir
<div class="h2" id="tracing-memory-leaks">
<h2>Tracking down memory leaks
- <a class="sectionlink" href="#tracing-memory-leaks"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_DEBUGGING_PAGE" -->#tracing-memory-leaks"
title="Link to this section">¶</a>
</h2>
Modified: subversion/site/publish/docs/community-guide/general.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/general.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/general.html (original)
+++ subversion/site/publish/docs/community-guide/general.html Fri Jul 23 16:24:34 2010
@@ -15,6 +15,16 @@
<div id="site-content">
<!--#include virtual="/site-notice.html" -->
+<!--#set var="GUIDE_BUILDING_PAGE" value="building.html" -->
+<!--#set var="GUIDE_CONVENTIONS_PAGE" value="conventions.html" -->
+<!--#set var="GUIDE_DEBUGGING_PAGE" value="debugging.html" -->
+<!--#set var="GUIDE_GENERAL_PAGE" value="general.html" -->
+<!--#set var="GUIDE_ISSUES_PAGE" value="issues.html" -->
+<!--#set var="GUIDE_L10N_PAGE" value="l10n.html" -->
+<!--#set var="GUIDE_MAILINGLISTS_PAGE" value="mailing-lists.html" -->
+<!--#set var="GUIDE_RELEASING_PAGE" value="releasing.html" -->
+<!--#set var="GUIDE_ROLES_PAGE" value="roles.html" -->
+
<!--#include virtual="guide-nav.html" -->
<!--#include virtual="general.part.html" -->
Modified: subversion/site/publish/docs/community-guide/general.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/general.part.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/general.part.html (original)
+++ subversion/site/publish/docs/community-guide/general.part.html Fri Jul 23 16:24:34 2010
@@ -1,6 +1,6 @@
<div class="h1" id="general">
<h1>General Overview
- <a class="sectionlink" href="#general"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#general"
title="Link to this section">¶</a>
</h1>
@@ -8,7 +8,7 @@
<div class="h2" id="participating">
<h2>Participating in the community
- <a class="sectionlink" href="#participating"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#participating"
title="Link to this section">¶</a>
</h2>
@@ -86,7 +86,7 @@ don't annoy others, and don't become eas
<div class="h2" id="docs">
<h2>Theory and documentation
- <a class="sectionlink" href="#docs"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#docs"
title="Link to this section">¶</a>
</h2>
@@ -101,7 +101,7 @@ don't annoy others, and don't become eas
</li>
<li><p>API Documentation</p>
- <p>See the section on the <a href="#doxygen-docs">public API
+ <p>See the section on the <a href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#doxygen-docs">public API
documentation</a> for more information.</p>
</li>
@@ -157,7 +157,7 @@ href="http://svn.apache.org/repos/asf/su
<div class="h2" id="code-to-read">
<h2>Code to read
- <a class="sectionlink" href="#code-to-read"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#code-to-read"
title="Link to this section">¶</a>
</h2>
@@ -218,7 +218,7 @@ to ask for review on the developer maili
<div class="h2" id="directory-layout">
<h2>Directory layout
- <a class="sectionlink" href="#directory-layout"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#directory-layout"
title="Link to this section">¶</a>
</h2>
@@ -295,7 +295,7 @@ to ask for review on the developer maili
<div class="h2" id="branch-policy">
<h2>Branching policy
- <a class="sectionlink" href="#branch-policy"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#branch-policy"
title="Link to this section">¶</a>
</h2>
@@ -320,7 +320,7 @@ development work go smoothly.</p>
<div class="h3" id="branch-creation-and-management">
<h3>Branch creation and management
- <a class="sectionlink" href="#branch-creation-and-management"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#branch-creation-and-management"
title="Link to this section">¶</a>
</h3>
@@ -337,7 +337,7 @@ roots of branches) is highly encouraged.
<div class="h3" id="lightweight-branches">
<h3>Lightweight branches
- <a class="sectionlink" href="#lightweight-branches"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#lightweight-branches"
title="Link to this section">¶</a>
</h3>
@@ -366,7 +366,7 @@ out which ones they are.</p>
either merged it to trunk or given up on it — please
remember to remove it.</p>
-<p>See also the <a href="#partial-commit-access" >section on partial
+<p>See also the <a href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#partial-commit-access" >section on partial
commit access</a> for our policy on offering commit access to
experimental branches.</p>
@@ -374,7 +374,7 @@ experimental branches.</p>
<div class="h3" id="branch-readme-files">
<h3>BRANCH-README files
- <a class="sectionlink" href="#branch-readme-files"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#branch-readme-files"
title="Link to this section">¶</a>
</h3>
@@ -435,13 +435,13 @@ delete the <tt>BRANCH-README</tt> file.<
<div class="h2" id="documenting">
<h2>Documentation
- <a class="sectionlink" href="#documenting"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#documenting"
title="Link to this section">¶</a>
</h2>
<div class="h3" id="document-everything">
<h3>Document Everything
- <a class="sectionlink" href="#document-everything"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#document-everything"
title="Link to this section">¶</a>
</h3>
@@ -520,7 +520,7 @@ subversion/include/*.h</a> for doxygen e
<div class="h3" id="doxygen-docs">
<h3>Public API Documentation
- <a class="sectionlink" href="#doxygen-docs"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#doxygen-docs"
title="Link to this section">¶</a>
</h3>
@@ -558,12 +558,13 @@ manual</a> for a complete list of comman
<div class="h2" id="patches">
<h2>Patch submission guidelines
- <a class="sectionlink" href="#patches"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#patches"
title="Link to this section">¶</a>
</h2>
<p>Mail patches to dev@subversion.apache.org, starting the subject line with
-<tt>[PATCH]</tt>. This helps our <a href="roles.html#patch-manager">patch manager</a>
+<tt>[PATCH]</tt>. This helps our
+<a href="<!--#echo var="GUIDE_ROLES_PAGE" -->#patch-manager">patch manager</a>
spot patches right away. For example:</p>
<pre>
@@ -589,7 +590,7 @@ helps potential reviewers understand the
increases the likelihood that it will be applied. You can put the log
message in the body of the email, or at the top of the patch
attachment (see below). Either way, it should follow the guidelines
-given in <a href="#log-messages">Writing log messages</a>, and be
+given in <a href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#log-messages">Writing log messages</a>, and be
enclosed in triple square brackets, like so:</p>
<pre>
@@ -626,7 +627,7 @@ the bug in detail and give a reproductio
these guidelines is when the patch addresses a specific issue in the
issues database — in that case, just refer to the
issue number in your log message, as described
-in <a href="#log-messages">Writing log messages</a>.</p>
+in <a href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#log-messages">Writing log messages</a>.</p>
<p>It is normal for patches to undergo several rounds of feedback and
change before being applied. Don't be discouraged if your patch is
Modified: subversion/site/publish/docs/community-guide/issues.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/issues.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/issues.html (original)
+++ subversion/site/publish/docs/community-guide/issues.html Fri Jul 23 16:24:34 2010
@@ -15,6 +15,16 @@
<div id="site-content">
<!--#include virtual="/site-notice.html" -->
+<!--#set var="GUIDE_BUILDING_PAGE" value="building.html" -->
+<!--#set var="GUIDE_CONVENTIONS_PAGE" value="conventions.html" -->
+<!--#set var="GUIDE_DEBUGGING_PAGE" value="debugging.html" -->
+<!--#set var="GUIDE_GENERAL_PAGE" value="general.html" -->
+<!--#set var="GUIDE_ISSUES_PAGE" value="issues.html" -->
+<!--#set var="GUIDE_L10N_PAGE" value="l10n.html" -->
+<!--#set var="GUIDE_MAILINGLISTS_PAGE" value="mailing-lists.html" -->
+<!--#set var="GUIDE_RELEASING_PAGE" value="releasing.html" -->
+<!--#set var="GUIDE_ROLES_PAGE" value="roles.html" -->
+
<!--#include virtual="guide-nav.html" -->
<!--#include virtual="issues.part.html" -->
Modified: subversion/site/publish/docs/community-guide/issues.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/issues.part.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/issues.part.html (original)
+++ subversion/site/publish/docs/community-guide/issues.part.html Fri Jul 23 16:24:34 2010
@@ -1,6 +1,6 @@
<div class="h1" id="issues">
<h1>Bugs / Issues
- <a class="sectionlink" href="#issues"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#issues"
title="Link to this section">¶</a>
</h1>
@@ -67,7 +67,7 @@ reporting problems or requested enhancem
<div class="h2" id="reporting-bugs">
<h2>How to report a bug
- <a class="sectionlink" href="#reporting-bugs"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#reporting-bugs"
title="Link to this section">¶</a>
</h2>
@@ -132,7 +132,7 @@ obvious to someone else, so it's best to
Follow that with the environment description, and the reproduction
recipe. If you also want to include speculation as to the cause, and
even a patch to fix the bug, that's great — see the <a
-href="#patches">patch submission guidelines</a>.</p>
+href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#patches">patch submission guidelines</a>.</p>
<p>Post all of this information to <a
href="mailto:dev@subversion.apache.org"
@@ -150,7 +150,7 @@ make the bug much more likely to get fix
<div class="h2" id="bugs-where">
<h2>Where to report a bug
- <a class="sectionlink" href="#bugs-where"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#bugs-where"
title="Link to this section">¶</a>
</h2>
@@ -200,7 +200,7 @@ make the bug much more likely to get fix
<div class="h2" id="issue-triage">
<h2>Issue triage
- <a class="sectionlink" href="#issue-triage"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ISSUES_PAGE" -->#issue-triage"
title="Link to this section">¶</a>
</h2>
Modified: subversion/site/publish/docs/community-guide/l10n.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/l10n.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/l10n.html (original)
+++ subversion/site/publish/docs/community-guide/l10n.html Fri Jul 23 16:24:34 2010
@@ -15,6 +15,16 @@
<div id="site-content">
<!--#include virtual="/site-notice.html" -->
+<!--#set var="GUIDE_BUILDING_PAGE" value="building.html" -->
+<!--#set var="GUIDE_CONVENTIONS_PAGE" value="conventions.html" -->
+<!--#set var="GUIDE_DEBUGGING_PAGE" value="debugging.html" -->
+<!--#set var="GUIDE_GENERAL_PAGE" value="general.html" -->
+<!--#set var="GUIDE_ISSUES_PAGE" value="issues.html" -->
+<!--#set var="GUIDE_L10N_PAGE" value="l10n.html" -->
+<!--#set var="GUIDE_MAILINGLISTS_PAGE" value="mailing-lists.html" -->
+<!--#set var="GUIDE_RELEASING_PAGE" value="releasing.html" -->
+<!--#set var="GUIDE_ROLES_PAGE" value="roles.html" -->
+
<!--#include virtual="guide-nav.html" -->
<!--#include virtual="l10n.part.html" -->
Modified: subversion/site/publish/docs/community-guide/l10n.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/l10n.part.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/l10n.part.html (original)
+++ subversion/site/publish/docs/community-guide/l10n.part.html Fri Jul 23 16:24:34 2010
@@ -1,6 +1,6 @@
<div class="h1" id="l10n">
<h1>Localization (l10n)
- <a class="sectionlink" href="#l10n"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#l10n"
title="Link to this section">¶</a>
</h1>
@@ -16,7 +16,7 @@ libraries.</p>
<div class="h2" id="l10n-overview">
<h2>Localization overview
- <a class="sectionlink" href="#l10n-overview"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#l10n-overview"
title="Link to this section">¶</a>
</h2>
@@ -80,7 +80,7 @@ href="http://subversion.tigris.org/servl
<div class="h2" id="version-requirements">
<h2>Software version requirements
- <a class="sectionlink" href="#version-requirements"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#version-requirements"
title="Link to this section">¶</a>
</h2>
@@ -93,7 +93,7 @@ for those wanting to compile the *.po fi
<div class="h2" id="new-translation">
<h2>Starting a new translation
- <a class="sectionlink" href="#new-translation"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#new-translation"
title="Link to this section">¶</a>
</h2>
@@ -107,7 +107,7 @@ intentions might help you find supporter
<div class="h3" id="unix-gnu-gettext">
<h3>Unix (GNU gettext)
- <a class="sectionlink" href="#unix-gnu-gettext"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#unix-gnu-gettext"
title="Link to this section">¶</a>
</h3>
@@ -126,7 +126,7 @@ intentions might help you find supporter
<p>Steps (2) and (3) generate a Makefile; step (4) generates
<code>subversion/po/subversion.pot</code></p>
-<p>The Subversion project has <a href="#other-conventions">a
+<p>The Subversion project has <a href="<!--#echo var="GUIDE_L10N_PAGE" -->#other-conventions">a
policy</a> not to put names in its files, so please apply the two changes
described below.</p>
@@ -176,7 +176,7 @@ these:</p>
<div class="h3" id="unix-nongnu-gettext">
<h3>Unix (non-GNU gettext)
- <a class="sectionlink" href="#unix-nongnu-gettext"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#unix-nongnu-gettext"
title="Link to this section">¶</a>
</h3>
@@ -186,7 +186,7 @@ these:</p>
<div class="h3" id="windows">
<h3>Windows
- <a class="sectionlink" href="#windows"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#windows"
title="Link to this section">¶</a>
</h3>
@@ -200,7 +200,7 @@ these:</p>
<div class="h2" id="verifying">
<h2>Verifying your po file
- <a class="sectionlink" href="#verifying"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#verifying"
title="Link to this section">¶</a>
</h2>
@@ -223,7 +223,7 @@ and 2 are only needed once after you hav
<div class="h2" id="submitting">
<h2>Submitting your po file
- <a class="sectionlink" href="#submitting"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#submitting"
title="Link to this section">¶</a>
</h2>
@@ -243,7 +243,7 @@ have been satisfied.</p>
<div class="h2" id="updating">
<h2>Updating existing po files
- <a class="sectionlink" href="#updating"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#updating"
title="Link to this section">¶</a>
</h2>
@@ -283,7 +283,7 @@ done. This has two advantages:</p>
<div class="h2" id="branch-maintenance">
<h2>Maintenance on branches
- <a class="sectionlink" href="#branch-maintenance"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#branch-maintenance"
title="Link to this section">¶</a>
</h2>
@@ -327,7 +327,7 @@ copy can be done with this command:</p>
<div class="h2" id="po-mo-requirements">
<h2>Requirements for po and mo files
- <a class="sectionlink" href="#po-mo-requirements"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#po-mo-requirements"
title="Link to this section">¶</a>
</h2>
@@ -353,7 +353,7 @@ safely ignore these warnings.
<div class="h2" id="empty-string-conventions">
<h2>Conventions for the empty string msgid section
- <a class="sectionlink" href="#empty-string-conventions"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#empty-string-conventions"
title="Link to this section">¶</a>
</h2>
@@ -373,7 +373,7 @@ this field.</p>
<div class="h2" id="translation-teams">
<h2>Translation teams
- <a class="sectionlink" href="#translation-teams"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#translation-teams"
title="Link to this section">¶</a>
</h2>
@@ -387,7 +387,7 @@ teams have guidelines to stimulate consi
<div class="h2" id="quotes">
<h2>Single versus double quotes
- <a class="sectionlink" href="#quotes"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#quotes"
title="Link to this section">¶</a>
</h2>
@@ -401,12 +401,12 @@ guidelines elsewhere in this guide. If
<div class="h2" id="translating-error-messages">
<h2>Error message conventions
- <a class="sectionlink" href="#translating-error-messages"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_L10N_PAGE" -->#translating-error-messages"
title="Link to this section">¶</a>
</h2>
<p>Since translators will generally see all error messages in the code,
-it's important to know that there is a <a href="#error-messages">
+it's important to know that there is a <a href="<!--#echo var="GUIDE_L10N_PAGE" -->#error-messages">
special section</a> in this document about this category of strings.
Here the same applies as does for the quotes: Adhere to them on all points
for which there is no explicit policy set out by the translation team for your
Modified: subversion/site/publish/docs/community-guide/mailing-lists.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/mailing-lists.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/mailing-lists.html (original)
+++ subversion/site/publish/docs/community-guide/mailing-lists.html Fri Jul 23 16:24:34 2010
@@ -15,6 +15,16 @@
<div id="site-content">
<!--#include virtual="/site-notice.html" -->
+<!--#set var="GUIDE_BUILDING_PAGE" value="building.html" -->
+<!--#set var="GUIDE_CONVENTIONS_PAGE" value="conventions.html" -->
+<!--#set var="GUIDE_DEBUGGING_PAGE" value="debugging.html" -->
+<!--#set var="GUIDE_GENERAL_PAGE" value="general.html" -->
+<!--#set var="GUIDE_ISSUES_PAGE" value="issues.html" -->
+<!--#set var="GUIDE_L10N_PAGE" value="l10n.html" -->
+<!--#set var="GUIDE_MAILINGLISTS_PAGE" value="mailing-lists.html" -->
+<!--#set var="GUIDE_RELEASING_PAGE" value="releasing.html" -->
+<!--#set var="GUIDE_ROLES_PAGE" value="roles.html" -->
+
<!--#include virtual="guide-nav.html" -->
<!--#include virtual="mailing-lists.part.html" -->
Modified: subversion/site/publish/docs/community-guide/mailing-lists.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/mailing-lists.part.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/mailing-lists.part.html (original)
+++ subversion/site/publish/docs/community-guide/mailing-lists.part.html Fri Jul 23 16:24:34 2010
@@ -1,6 +1,6 @@
<div class="h1" id="mailing-lists">
<h1>Mailing Lists
- <a class="sectionlink" href="#mailing-lists"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#mailing-lists"
title="Link to this section">¶</a>
</h1>
@@ -18,7 +18,7 @@ your post is much more likely to be read
<div class="h2" id="where-to-post">
<h2>Where to post
- <a class="sectionlink" href="#where-to-post"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#where-to-post"
title="Link to this section">¶</a>
</h2>
@@ -42,7 +42,7 @@ unfortunate, but it does not make the qu
<p>Of course, if the mail is about a possible bug in Subversion, and
got no reaction on users@, then asking on dev@ is
fine — bugs are a development topic.
-And <a href="#patches" >patches</a> should always be sent directly to
+And <a href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#patches" >patches</a> should always be sent directly to
dev@.</p>
</div> <!-- where-to-post -->
@@ -50,7 +50,7 @@ dev@.</p>
<div class="h2" id="when-to-post">
<h2>When to post
- <a class="sectionlink" href="#when-to-post"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#when-to-post"
title="Link to this section">¶</a>
</h2>
@@ -70,13 +70,13 @@ diverge.</p>
<div class="h2" id="formatting">
<h2>Formatting
- <a class="sectionlink" href="#formatting"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#formatting"
title="Link to this section">¶</a>
</h2>
<div class="h3" id="line-length">
<h3>Line Length
- <a class="sectionlink" href="#line-length"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#line-length"
title="Link to this section">¶</a>
</h3>
@@ -85,7 +85,7 @@ diverge.</p>
columns, you leave room for quoting characters to be added in future
replies without forcing a rewrapping of the text. The 72-column limit
only applies to the prose part of your message, of course. If you're
-posting a patch, see <a href="#patches">the section on
+posting a patch, see <a href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#patches">the section on
patches</a>.</p>
<p>Some mailers do a kind of automatic line-wrapping, whereby when
@@ -98,7 +98,7 @@ for a setting you can tweak to make it s
<div class="h3" id="capitalization">
<h3>Capitalization
- <a class="sectionlink" href="#capitalization"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#capitalization"
title="Link to this section">¶</a>
</h3>
@@ -115,13 +115,13 @@ and many people will not bother to read
<div class="h2" id="replying">
<h2>Replying
- <a class="sectionlink" href="#replying"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#replying"
title="Link to this section">¶</a>
</h2>
<div class="h3" id="reply-to">
<h3>Reply-To
- <a class="sectionlink" href="#reply-to"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#reply-to"
title="Link to this section">¶</a>
</h3>
@@ -155,7 +155,7 @@ topic.</p>
<div class="h3" id="fresh-post">
<h3>Making a fresh post
- <a class="sectionlink" href="#fresh-post"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#fresh-post"
title="Link to this section">¶</a>
</h3>
@@ -182,7 +182,7 @@ it show a distinction.)</p>
<div class="h3" id="rethreading">
<h3>Re-threading
- <a class="sectionlink" href="#rethreading"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#rethreading"
title="Link to this section">¶</a>
</h3>
@@ -205,7 +205,7 @@ the old subject in parenthesis, like thi
<div class="h3" id="top-posting">
<h3>Top-Posting
- <a class="sectionlink" href="#top-posting"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#top-posting"
title="Link to this section">¶</a>
</h3>
@@ -236,11 +236,11 @@ href="http://www.netmeister.org/news/lea
<div class="h2" id="sending-patches">
<h2>Sending patches
- <a class="sectionlink" href="#sending-patches"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#sending-patches"
title="Link to this section">¶</a>
</h2>
-<p>See <a href="general.html#patches">here</a> for advice on how to send in a
+<p>See <a href="<!--#echo var="GUIDE_GENERAL_PAGE" -->#patches">here</a> for advice on how to send in a
patch. Note that you can send in a patch to modify these web pages as
well as to modify code; the web pages' repository URL is
<a href="http://svn.apache.org/repos/asf/subversion/site/"
@@ -251,7 +251,7 @@ well as to modify code; the web pages' r
<div class="h2" id="encodings">
<h2>Languages and encodings
- <a class="sectionlink" href="#encodings"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_MAILINGLISTS_PAGE" -->#encodings"
title="Link to this section">¶</a>
</h2>
Modified: subversion/site/publish/docs/community-guide/releasing.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.html Fri Jul 23 16:24:34 2010
@@ -15,6 +15,16 @@
<div id="site-content">
<!--#include virtual="/site-notice.html" -->
+<!--#set var="GUIDE_BUILDING_PAGE" value="building.html" -->
+<!--#set var="GUIDE_CONVENTIONS_PAGE" value="conventions.html" -->
+<!--#set var="GUIDE_DEBUGGING_PAGE" value="debugging.html" -->
+<!--#set var="GUIDE_GENERAL_PAGE" value="general.html" -->
+<!--#set var="GUIDE_ISSUES_PAGE" value="issues.html" -->
+<!--#set var="GUIDE_L10N_PAGE" value="l10n.html" -->
+<!--#set var="GUIDE_MAILINGLISTS_PAGE" value="mailing-lists.html" -->
+<!--#set var="GUIDE_RELEASING_PAGE" value="releasing.html" -->
+<!--#set var="GUIDE_ROLES_PAGE" value="roles.html" -->
+
<!--#include virtual="guide-nav.html" -->
<!--#include virtual="releasing.part.html" -->
Modified: subversion/site/publish/docs/community-guide/releasing.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/releasing.part.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/releasing.part.html (original)
+++ subversion/site/publish/docs/community-guide/releasing.part.html Fri Jul 23 16:24:34 2010
@@ -1,6 +1,6 @@
<div class="h1" id="releasing">
<h1>Making Subversion Releases
- <a class="sectionlink" href="#releasing"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#releasing"
title="Link to this section">¶</a>
</h1>
@@ -8,7 +8,7 @@
<div class="h2" id="release-numbering">
<h2>Release numbering, compatibility, and deprecation
- <a class="sectionlink" href="#release-numbering"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#release-numbering"
title="Link to this section">¶</a>
</h2>
@@ -145,7 +145,7 @@ prereleases leading to 1.3.7 might look
version 1.3.7
</pre>
-<p>(See <a href="#alphas-betas">this section</a> for more information
+<p>(See <a href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#alphas-betas">this section</a> for more information
about when and how we do alpha and beta releases.)</p>
<p>When you 'make install' subversion-1.3.7-rc1, it still installs as
@@ -172,14 +172,14 @@ copies, we put out a prerelease.</p>
<div class="h3" id="name-reuse">
<h3>Reuse of release names
- <a class="sectionlink" href="#name-reuse"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#name-reuse"
title="Link to this section">¶</a>
</h3>
<p>If a release or candidate release needs to be quickly re-issued due
to some non-code problem (say, a packaging glitch), it's okay to reuse
the same name, as long as the tarball hasn't been
-<a href="#tarball-signing">blessed by signing</a> yet. But if it has
+<a href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#tarball-signing">blessed by signing</a> yet. But if it has
been uploaded to the standard distribution area with signatures, or if
the re-issue was due to a change in code a user might run, then the
old name must be tossed and the next name used.</p>
@@ -188,7 +188,7 @@ old name must be tossed and the next nam
<div class="h3" id="deprecation">
<h3>Deprecation
- <a class="sectionlink" href="#deprecation"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#deprecation"
title="Link to this section">¶</a>
</h3>
@@ -244,7 +244,7 @@ because its new name is fine.</p>
<div class="h2" id="release-stabilization">
<h2>Stabilizing and maintaining releases
- <a class="sectionlink" href="#release-stabilization"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#release-stabilization"
title="Link to this section">¶</a>
</h2>
@@ -404,7 +404,7 @@ not voted for those revisions, as follow
</pre>
<p>If in case votes have been communicated via IRC or other means,
-note that in the log message. <a href="#obvious-fix">Obvious fixes</a>
+note that in the log message. <a href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#obvious-fix">Obvious fixes</a>
do not require '(rX only)' to be mentioned.</p>
<p>Voting +1 on a change doesn't just mean you approve of it in
@@ -477,13 +477,13 @@ voting, are always kept on the main rele
<div class="h3" id="alphas-betas">
<h2>Alpha and beta releases
- <a class="sectionlink" href="#alphas-betas"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#alphas-betas"
title="Link to this section">¶</a>
</h2>
<p>When we want new features to get wide testing before we enter the
formal stabilization period described above, we'll sometimes release
-alpha and beta tarballs (as <a href="#release-numbering" >shown
+alpha and beta tarballs (as <a href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#release-numbering" >shown
earlier</a>). The line between alpha and beta is fuzzy, but
basically, "alpha" means "we know or expect there are problems", and
"beta" means "we don't expect problems". There is no requirement to
@@ -515,7 +515,7 @@ href="http://subversion.tigris.org/servl
<div class="h2" id="tarball-signing">
<h2>Signing source distribution packages (a.k.a tarballs)
- <a class="sectionlink" href="#tarball-signing"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#tarball-signing"
title="Link to this section">¶</a>
</h2>
@@ -570,7 +570,7 @@ manager.</p>
<div class="h2" id="custom-releases">
<h2>Custom releases
- <a class="sectionlink" href="#custom-releases"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#custom-releases"
title="Link to this section">¶</a>
</h2>
@@ -605,7 +605,7 @@ keep them as temporary and as non-diverg
<div class="h2" id="release-branches">
<h2>Creating and maintaining release branches
- <a class="sectionlink" href="#release-branches"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#release-branches"
title="Link to this section">¶</a>
</h2>
@@ -671,7 +671,7 @@ A.B with the version you're preparing, e
<div class="h2" id="porting-changes">
<h2>Porting changes to release branches
- <a class="sectionlink" href="#porting-changes"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#porting-changes"
title="Link to this section">¶</a>
</h2>
@@ -682,7 +682,7 @@ in from trunk.</p>
<p>The protocol used to accept or refuse the merging of changes from
trunk is of interest to all Subversion developers, and as such is
-documented in <a href="#release-stabilization">the
+documented in <a href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#release-stabilization">the
release stabilization section</a>.</p>
</div> <!-- porting-changes -->
@@ -690,7 +690,7 @@ release stabilization section</a>.</p>
<div class="h2" id="the-changes-file">
<h2>Managing the CHANGES file
- <a class="sectionlink" href="#the-changes-file"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#the-changes-file"
title="Link to this section">¶</a>
</h2>
@@ -723,7 +723,7 @@ detailed?</i></p>
<div class="h3" id="writing-initial-changes">
<h3>Writing the initial content for a branch
- <a class="sectionlink" href="#writing-initial-changes"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#writing-initial-changes"
title="Link to this section">¶</a>
</h3>
@@ -750,11 +750,11 @@ keep things consistent.</p>
<div class="h3" id="adding-changes">
<h3>Adding content for patch release
- <a class="sectionlink" href="#adding-changes"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#adding-changes"
title="Link to this section">¶</a>
</h3>
-<p>As part of <a href="#release-stabilization">release
+<p>As part of <a href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#release-stabilization">release
stabilization</a>, <tt>CHANGES</tt> should be updated as bug fixes are
ported to the release branch. Generally, if you merge a revision or group
of revisions (i.e., an item in <tt>STATUS</tt>) to the release branch, you
@@ -769,7 +769,7 @@ branch when a patch release is made.</p>
<div class="h2" id="before-release">
<h2>Preparing to roll a release
- <a class="sectionlink" href="#before-release"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#before-release"
title="Link to this section">¶</a>
</h2>
@@ -844,7 +844,7 @@ Do not use symlinks, <tt>dist.sh</tt> do
<div class="h2" id="rolling-release">
<h2>Rolling a release
- <a class="sectionlink" href="#rolling-release"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#rolling-release"
title="Link to this section">¶</a>
</h2>
@@ -987,7 +987,7 @@ so on.</p>
<div class="h2" id="releasing-release">
<h2>The actual releasing
- <a class="sectionlink" href="#releasing-release"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#releasing-release"
title="Link to this section">¶</a>
</h2>
@@ -1084,7 +1084,7 @@ series. Commit those changes, too.</li>
<div class="h2" id="afterwards">
<h2>After a release has been made
- <a class="sectionlink" href="#afterwards"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#afterwards"
title="Link to this section">¶</a>
</h2>
@@ -1098,7 +1098,7 @@ manager.)</p>
<div class="h3" id="releasing-not">
<h3>How <em>not</em> to make a Subversion release
- <a class="sectionlink" href="#releasing-not"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_RELEASING_PAGE" -->#releasing-not"
title="Link to this section">¶</a>
</h3>
Modified: subversion/site/publish/docs/community-guide/roles.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/roles.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/roles.html (original)
+++ subversion/site/publish/docs/community-guide/roles.html Fri Jul 23 16:24:34 2010
@@ -15,6 +15,16 @@
<div id="site-content">
<!--#include virtual="/site-notice.html" -->
+<!--#set var="GUIDE_BUILDING_PAGE" value="building.html" -->
+<!--#set var="GUIDE_CONVENTIONS_PAGE" value="conventions.html" -->
+<!--#set var="GUIDE_DEBUGGING_PAGE" value="debugging.html" -->
+<!--#set var="GUIDE_GENERAL_PAGE" value="general.html" -->
+<!--#set var="GUIDE_ISSUES_PAGE" value="issues.html" -->
+<!--#set var="GUIDE_L10N_PAGE" value="l10n.html" -->
+<!--#set var="GUIDE_MAILINGLISTS_PAGE" value="mailing-lists.html" -->
+<!--#set var="GUIDE_RELEASING_PAGE" value="releasing.html" -->
+<!--#set var="GUIDE_ROLES_PAGE" value="roles.html" -->
+
<!--#include virtual="guide-nav.html" -->
<!--#include virtual="roles.part.html" -->
Modified: subversion/site/publish/docs/community-guide/roles.part.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/roles.part.html?rev=967156&r1=967155&r2=967156&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/roles.part.html (original)
+++ subversion/site/publish/docs/community-guide/roles.part.html Fri Jul 23 16:24:34 2010
@@ -1,6 +1,6 @@
<div class="h1" id="roles">
<h1>Community Roles
- <a class="sectionlink" href="#roles"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ROLES_PAGE" -->#roles"
title="Link to this section">¶</a>
</h1>
@@ -8,7 +8,7 @@
<div class="h2" id="committers">
<h2>Committers
- <a class="sectionlink" href="#committers"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ROLES_PAGE" -->#committers"
title="Link to this section">¶</a>
</h2>
@@ -28,7 +28,7 @@ says the domains for each partial commit
<div class="h3" id="full-commit-access">
<h3>How full commit access is granted
- <a class="sectionlink" href="#full-commit-access"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ROLES_PAGE" -->#full-commit-access"
title="Link to this section">¶</a>
</h3>
@@ -63,7 +63,7 @@ whose only purpose is to gain commit acc
patch post and what's not is part of showing good judgement :-) .)</p>
<p>To assist developers in discovering new committers, we record
-patches and other contributions in a <a href="#crediting">special
+patches and other contributions in a <a href="<!--#echo var="GUIDE_ROLES_PAGE" -->#crediting">special
crediting format</a>, which is then parsed to produce a
browser-friendly <a
href="http://www.red-bean.com/svnproject/contribulyzer/">contribution
@@ -76,7 +76,7 @@ list</a> might be the most convenient pl
<div class="h3" id="partial-commit-access">
<h3>How partial commit access is granted
- <a class="sectionlink" href="#partial-commit-access"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ROLES_PAGE" -->#partial-commit-access"
title="Link to this section">¶</a>
</h3>
@@ -107,7 +107,7 @@ committers, actually — view s
grounds for new developers, by giving feedback on the commits. The
goal of these branches is both to get new code into Subversion and to
get new developers into the project. See also the <a
-href="#lightweight-branches" >section on lightweight branches</a>, and
+href="<!--#echo var="GUIDE_ROLES_PAGE" -->#lightweight-branches" >section on lightweight branches</a>, and
this mail:</p>
<pre>
@@ -124,7 +124,7 @@ this mail:</p>
<div class="h3" id="contrib-area">
<h3>The contrib/ area
- <a class="sectionlink" href="#contrib-area"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ROLES_PAGE" -->#contrib-area"
title="Link to this section">¶</a>
</h3>
@@ -143,7 +143,7 @@ license or copyright holder as Subversio
<div class="h3" id="obvious-fix">
<h3>The "obvious fix" rule
- <a class="sectionlink" href="#obvious-fix"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ROLES_PAGE" -->#obvious-fix"
title="Link to this section">¶</a>
</h3>
@@ -154,7 +154,7 @@ comments, commit messages, etc. We rely
to determine what is "obvious"; if you're not sure, just ask.</p>
<p>Whenever you invoke the "obvious fix" rule, please say so in
-the <a href="#log-messages">log message</a> of your commit. For example:</p>
+the <a href="<!--#echo var="GUIDE_ROLES_PAGE" -->#log-messages">log message</a> of your commit. For example:</p>
<pre>
------------------------------------------------------------------------
@@ -178,7 +178,7 @@ Obvious fix.
<div class="h2" id="release-manager">
<h2>Release Manager
- <a class="sectionlink" href="#release-manager"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ROLES_PAGE" -->#release-manager"
title="Link to this section">¶</a>
</h2>
@@ -215,7 +215,7 @@ Hyrum Wright <hyrum.wright@wandisco.c
<div class="h2" id="patch-manager">
<h2>Patch Manager
- <a class="sectionlink" href="#patch-manager"
+ <a class="sectionlink" href="<!--#echo var="GUIDE_ROLES_PAGE" -->#patch-manager"
title="Link to this section">¶</a>
</h2>