incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject svn commit: r1182994 [7/42] - in /incubator/public/trunk/site-publish: ./ audit/ guides/ incubation/ ip-clearance/ learn/ official/ projects/ projects/geronimo/
Date Thu, 13 Oct 2011 17:17:36 GMT
Modified: incubator/public/trunk/site-publish/guides/releasemanagement.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/releasemanagement.html?rev=1182994&r1=1182993&r2=1182994&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasemanagement.html [utf-8] (original)
+++ incubator/public/trunk/site-publish/guides/releasemanagement.html [utf-8] Thu Oct 13 17:17:19 2011
@@ -48,49 +48,49 @@
      <input name="Search" value="Go" type="submit"/>
     </form>
           <div class="menuheader"><a 
-href="/projects/index.html">Incubator Projects</a></div> 
+href="../projects/index.html">Incubator Projects</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
 href="http://www.apache.org/foundation/glossary.html#Podling">Podlings (What's that?)</a></div> 
     <menu compact="compact">
-          <li><a href="/incubation/Incubation_Policy.html">How? (Policy)</a></li> 
-          <li><a href="/incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li> 
-          <li><a href="/incubation/Process_Description.html">When? (Process)</a></li> 
+          <li><a href="../incubation/Incubation_Policy.html">How? (Policy)</a></li> 
+          <li><a href="../incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li> 
+          <li><a href="../incubation/Process_Description.html">When? (Process)</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/guides/index.html">Entry Guides</a></div> 
+href="../guides/index.html">Entry Guides</a></div> 
     <menu compact="compact">
-          <li><a href="/guides/proposal.html">Proposal Guide</a></li> 
+          <li><a href="../guides/proposal.html">Proposal Guide</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/guides/index.html">Podling Guides</a></div> 
+href="../guides/index.html">Podling Guides</a></div> 
     <menu compact="compact">
-          <li><a href="/guides/committer.html">Podling Committers</a></li> 
-          <li><a href="/guides/ppmc.html">Podling PMC (PPMC)</a></li> 
-          <li><a href="/guides/mentor.html">Podling Mentor</a></li> 
-          <li><a href="/guides/releasemanagement.html">Podling Releases</a></li> 
-          <li><a href="/guides/branding.html">Podling Branding/Publicity</a></li> 
-          <li><a href="/guides/sites.html">Podling Websites</a></li> 
-          <li><a href="/guides/graduation.html">Graduation</a></li> 
-          <li><a href="/guides/retirement.html">Retirement</a></li> 
+          <li><a href="../guides/committer.html">Podling Committers</a></li> 
+          <li><a href="../guides/ppmc.html">Podling PMC (PPMC)</a></li> 
+          <li><a href="../guides/mentor.html">Podling Mentor</a></li> 
+          <li><a href="../guides/releasemanagement.html">Podling Releases</a></li> 
+          <li><a href="../guides/branding.html">Podling Branding/Publicity</a></li> 
+          <li><a href="../guides/sites.html">Podling Websites</a></li> 
+          <li><a href="../guides/graduation.html">Graduation</a></li> 
+          <li><a href="../guides/retirement.html">Retirement</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/clutch.html">Status of the Clutch</a></div> 
+href="../clutch.html">Status of the Clutch</a></div> 
     <menu compact="compact">
-          <li><a href="/clutch.html">Current Podling Status</a></li> 
-          <li><a href="/clutch.html#steps">Assist with Steps</a></li> 
+          <li><a href="../clutch.html">Current Podling Status</a></li> 
+          <li><a href="../clutch.html#steps">Assist with Steps</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/ip-clearance/index.html">IP Clearance</a></div> 
+href="../ip-clearance/index.html">IP Clearance</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
-href="/whoweare.html">Who We Are</a></div> 
+href="../whoweare.html">Who We Are</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
-href="/sitemap.html">Site Map</a></div> 
+href="../sitemap.html">Site Map</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
@@ -104,11 +104,11 @@ href="http://www.apache.org">ASF</a></di
             </menu>
       <div class="menuheader">Other Guides</div>
     <menu compact="compact">
-          <li><a href="/guides/participation.html">Participation</a></li> 
-          <li><a href="/faq.html">General FAQ</a></li> 
-          <li><a href="/guides/pmc.html">PMC</a> (<a href="/guides/chair.html">Chair</a>)</li> 
-          <li><a href="/guides/lists.html">Mailing Lists</a></li> 
-          <li><a href="/guides/website.html">Incubator Website</a></li> 
+          <li><a href="../guides/participation.html">Participation</a></li> 
+          <li><a href="../faq.html">General FAQ</a></li> 
+          <li><a href="../guides/pmc.html">PMC</a> (<a href="../guides/chair.html">Chair</a>)</li> 
+          <li><a href="../guides/lists.html">Mailing Lists</a></li> 
+          <li><a href="../guides/website.html">Incubator Website</a></li> 
             </menu>
       <div class="menuheader"><a 
 href="http://wiki.apache.org/incubator">Incubator Wiki</a></div> 
@@ -122,13 +122,9 @@ href="http://wiki.apache.org/incubator">
    </div>
    
    <div class="span12">
-            <h2><img src="../images/redarrow.gif" />
-   <a name="intro">A Guide To Release Management During Incubation (DRAFT)</a>
-</h2>
-<div class="section-content">
-<h3>
-   <a name="TOC">Contents</a>
-</h3>
+            <h2 id='intro'><img src="../images/redarrow.gif" />A Guide To Release Management During Incubation (DRAFT)</h2>
+<div class="section-content">
+<h3 id='TOC'>Contents</h3>
 <div class="section-content">
 <ul>
 <li><a href='#intro'>
@@ -663,18 +659,14 @@ Podling Distribution Directory
 </li>
 </ul>
 </div>
-<h3>
-   <a name="status">Status - DRAFT</a>
-</h3>
+<h3 id='status'>Status - DRAFT</h3>
 <div class="section-content">
 <p>
 This document is under active <a href="#help-wanted">development</a>. This is a first 
 draft intended to allow public review. 
           </p>
 </div>
-<h3>
-   <a name="abstract">Abstract</a>
-</h3>
+<h3 id='abstract'>Abstract</h3>
 <div class="section-content">
 <p>
 This document is descriptive, not normative. It aims to guide podlings through the process of release management.
@@ -688,9 +680,7 @@ with commentary and discusses incubation
 <a href="/incubation/Incubation_Policy.html#Releases">policy</a>. 
             </p>
 </div>
-<h3>
-   <a name="apache-releases">Apache Releases</a>
-</h3>
+<h3 id='apache-releases'>Apache Releases</h3>
 <div class="section-content">
 <p>
 Releases are important:
@@ -706,9 +696,7 @@ Releases at Apache involve more ceremony
 not only on the project but also the foundation as a whole. 
         </p>
 </div>
-<h3>
-   <a name="organisation">Organization</a>
-</h3>
+<h3 id='organisation'>Organization</h3>
 <div class="section-content">
 <p>
         This document is a collection of information related to best-practices for releases.
@@ -718,9 +706,7 @@ not only on the project but also the fou
         bits of information to consume as time permits.  Come back often, as the contents are
         always subject to change.
 			</p>
-<h4>
-   <a name="document-usage">Usage</a>
-</h4>
+<h4 id='document-usage'>Usage</h4>
 <div class="section-content">
 <p><strong>NOTE</strong> beta quality TODO: Improve PROSE, check content</p>
 <p>
@@ -757,9 +743,7 @@ not only on the project but also the fou
             </p>
 </div>
 </div>
-<h3>
-   <a name="help">Help Wanted!</a>
-</h3>
+<h3 id='help'>Help Wanted!</h3>
 <div class="section-content">
 <p>
 Help to finish this document by contributing documentation patches to the incubator general list!
@@ -773,9 +757,7 @@ that isn't included then please ask for 
 are encouraged.
     </p>
 </div>
-<h3>
-   <a name="references">References</a>
-</h3>
+<h3 id='references'>References</h3>
 <div class="section-content">
 <p>
         TODO: links to project management books.
@@ -785,14 +767,10 @@ are encouraged.
         </ul>
 </div>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="guidelines">Guidelines</a>
-</h2>
+        <h2 id='guidelines'><img src="../images/redarrow.gif" />Guidelines</h2>
 <div class="section-content">
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="managing subversion">Managing Your SVN Tree</a>
-</h2>
+        <h2 id='managing subversion'><img src="../images/redarrow.gif" />Managing Your SVN Tree</h2>
 <div class="section-content">
 <p>
         Leo Simons has written an excellent
@@ -800,9 +778,7 @@ are encouraged.
         on this subject.  Do read it!
       </p>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="release-distribution">Distributing Releases</a>
-</h2>
+        <h2 id='release-distribution'><img src="../images/redarrow.gif" />Distributing Releases</h2>
 <div class="section-content">
 <p>
       Once a release has been approved by the 
@@ -810,9 +786,7 @@ are encouraged.
       it needs to be uploaded to the servers for wider distribution. A description of this process and the policy
       governing it follows.
       </p>
-<h3>
-   <a name="distribution-policy-overview">Policy Overview</a>
-</h3>
+<h3 id='distribution-policy-overview'>Policy Overview</h3>
 <div class="section-content">
 <p>
         Distribution policy with regard to releases is simple:
@@ -845,13 +819,9 @@ are encouraged.
         guide for the podling.
         </p>
 </div>
-<h3>
-   <a name="understanding-distribution">Understanding Release Distribution</a>
-</h3>
-<div class="section-content">
-<h4>
-   <a name="understanding-upload">Uploading Artifacts</a>
-</h4>
+<h3 id='understanding-distribution'>Understanding Release Distribution</h3>
+<div class="section-content">
+<h4 id='understanding-upload'>Uploading Artifacts</h4>
 <div class="section-content">
 <p>
           The distribution upload location (<code>www.apache.org/dist</code>) for all Apache projects is the
@@ -872,9 +842,7 @@ are encouraged.
           to <code>scp</code> into the home directory and then copy into position from there.
           </p>
 </div>
-<h4>
-   <a name="understanding-mirroring">Mirroring</a>
-</h4>
+<h4 id='understanding-mirroring'>Mirroring</h4>
 <div class="section-content">
 <p>
           To avoid excessive use of bandwidth and to increase download speeds,
@@ -898,9 +866,7 @@ are encouraged.
           See <a href="http://www.apache.org/dev/release-signing.html">release signing guide</a> for more information.
           </p>
 </div>
-<h4>
-   <a name="understanding-archiving">Archiving</a>
-</h4>
+<h4 id='understanding-archiving'>Archiving</h4>
 <div class="section-content">
 <p>
           All Apache releases form an important part of the history of a project.
@@ -927,13 +893,9 @@ are encouraged.
           <a href="http://www.apache.org/dev/release.html#how-to-archive">how to archive</a>.
           </p>
 </div>
-<h4>
-   <a name="understanding-security">Security</a>
-</h4>
-<div class="section-content">
-<h5> 
-   <a name="distribution-permissions">Permissions</a> 
-</h5> 
+<h4 id='understanding-security'>Security</h4>
+<div class="section-content">
+<h5 id='distribution-permissions'>Permissions</h5> 
 <div class="section-content">
 <p>
         One group is created by infrastructure for each top level project. All releases 
@@ -968,9 +930,7 @@ are encouraged.
         will then be used.
             </p>
 </div>
-<h5> 
-   <a name="distribution-checksums-sigs">Sums And Signatures</a> 
-</h5> 
+<h5 id='distribution-checksums-sigs'>Sums And Signatures</h5> 
 <div class="section-content">
 <p>
         Start by reading the <a href="http://www.apache.org/dev/release-signing.html">guide</a> 
@@ -1008,9 +968,7 @@ are encouraged.
         This will ensure no false alarms from the infrastructure team. 
            </p>
 </div>
-<h5> 
-   <a name="distribution-modifications">Modifications</a> 
-</h5> 
+<h5 id='distribution-modifications'>Modifications</h5> 
 <div class="section-content">
 <p>
         Once an artifact has been uploaded, it must never be modified. Not only is there no
@@ -1025,9 +983,7 @@ are encouraged.
 </div>
 </div>
 </div>
-<h3>
-   <a name="distribution-check-list">Distribution Check List</a>
-</h3>
+<h3 id='distribution-check-list'>Distribution Check List</h3>
 <div class="section-content">
 <ul>
           <li>Directory is <code>www.apache.org/dist/incubator/<em>podling</em></code></li>
@@ -1039,13 +995,9 @@ are encouraged.
           refer to the originals on <code>www.apache.org</code></li>
         </ul>
 </div>
-<h3>
-   <a name="distribution-best-practice">Best Practice</a>
-</h3>
-<div class="section-content">
-<h4>
-   <a name="distribution-layout">Layout</a>
-</h4>
+<h3 id='distribution-best-practice'>Best Practice</h3>
+<div class="section-content">
+<h4 id='distribution-layout'>Layout</h4>
 <div class="section-content">
 <p>
             A podling is free to choose a suitable layout for its released
@@ -1061,9 +1013,7 @@ are encouraged.
             The mirroring and archiving infrastructure should work well
             with most choices.
           </p>
-<h5> 
-   <a name="distribution-layout-plain">Plain Artifacts</a> 
-</h5> 
+<h5 id='distribution-layout-plain'>Plain Artifacts</h5> 
 <div class="section-content">
 <p>
           All artifacts, checksums and signatures placed directly into the
@@ -1073,9 +1023,7 @@ are encouraged.
           is placed within the distribution directory.
             </p>
 </div>
-<h5> 
-   <a name="distribution-layout-misc">Miscellaneous Documents</a> 
-</h5> 
+<h5 id='distribution-layout-misc'>Miscellaneous Documents</h5> 
 <div class="section-content">
 <p>
             All files contained in <code>www.apache.org/dist</code> will be mirrored.
@@ -1094,9 +1042,7 @@ are encouraged.
             <code>FOOTER.html</code> documents allows the text of the index page to be customised.
             </p>
 </div>
-<h5> 
-   <a name="distribution-layout-structured">A Structured Layout</a> 
-</h5> 
+<h5 id='distribution-layout-structured'>A Structured Layout</h5> 
 <div class="section-content">
 <p>
             Many projects use structured layouts. For example:
@@ -1117,9 +1063,7 @@ are encouraged.
             </p>
 </div>
 </div>
-<h4>
-   <a name="distribution-release-documentation">Release Documentation</a>
-</h4>
+<h4 id='distribution-release-documentation'>Release Documentation</h4>
 <div class="section-content">
 <p>
           Many project distribute notices for a release (such as <code>RELEASE_NOTES</code>, 
@@ -1174,9 +1118,7 @@ are encouraged.
           mirroring. So that is recommended.
        </p>
 </div>
-<h4>
-   <a name="archiving-old-releases">Archiving Old Releases</a>
-</h4>
+<h4 id='archiving-old-releases'>Archiving Old Releases</h4>
 <div class="section-content">
 <p>
           Old releases should be archived 
@@ -1196,9 +1138,7 @@ are encouraged.
           incubator directory should be used.
           </p>
 </div>
-<h4>
-   <a name="distribution-mirroring">Mirroring Scripts</a>
-</h4>
+<h4 id='distribution-mirroring'>Mirroring Scripts</h4>
 <div class="section-content">
 <p>
           There are two options:
@@ -1235,9 +1175,7 @@ are encouraged.
           <a href="http://www.apache.org/dev/release-signing.html">signing guide</a>.
           </p>
 </div>
-<h4>
-   <a name="distribution-signing">Signatures</a>
-</h4>
+<h4 id='distribution-signing'>Signatures</h4>
 <div class="section-content">
 <p>
           Understand the <a href="http://www.apache.org/dev/release-signing.html">guide</a>.
@@ -1250,9 +1188,7 @@ are encouraged.
           It is recommended that all committers add their keys to that file.
           </p>
 </div>
-<h4>
-   <a name="distribution-defects">Dealing With A Defect</a>
-</h4>
+<h4 id='distribution-defects'>Dealing With A Defect</h4>
 <div class="section-content">
 <p>
         Once an artifact has been uploaded, it must never be modified. No matter how 
@@ -1276,9 +1212,7 @@ are encouraged.
           <li>Adding a suitable notice to the download page</li>
           </ol>
 </div>
-<h4>
-   <a name="distributing-eclipse">Eclipse Update Site</a>
-</h4>
+<h4 id='distributing-eclipse'>Eclipse Update Site</h4>
 <div class="section-content">
 <p>
           Podlings may distribute suitable artifacts through an 
@@ -1298,9 +1232,7 @@ are encouraged.
 </div>
 </div>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="check-list">Check List</a>
-</h2>
+        <h2 id='check-list'><img src="../images/redarrow.gif" />Check List</h2>
 <div class="section-content">
 <p>
 <strong>Note</strong> this is not intended to replace an understanding of the release process.
@@ -1353,9 +1285,7 @@ are encouraged.
          	</li>
         </ul>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="rules">Rules</a>
-</h2>
+        <h2 id='rules'><img src="../images/redarrow.gif" />Rules</h2>
 <div class="section-content">
 <p>
 Every incubator release is also an Apache release. So Apache policy must be followed. 
@@ -1371,9 +1301,7 @@ documentation on the main <a href="http:
 A few important topics are discussed below. These are a supplement and not a substitute 
 for the Apache documentation.
         </p>
-<h3>
-   <a name="signing">Signing</a>
-</h3>
+<h3 id='signing'>Signing</h3>
 <div class="section-content">
 <p>
  The release manager need to create a
@@ -1396,9 +1324,7 @@ and at least some of the background mate
                 </li>
             </ul>
 </div>
-<h3>
-   <a name="naming">Naming</a>
-</h3>
+<h3 id='naming'>Naming</h3>
 <div class="section-content">
 <p>
 Apache releases should contain the full name of the project responsible for the release. This ensures that
@@ -1430,9 +1356,7 @@ For example, for podling foo, both <code
                 </li>
             </ul>
 </div>
-<h3>
-   <a name="release-legal-audit">License Audit</a>
-</h3>
+<h3 id='release-legal-audit'>License Audit</h3>
 <div class="section-content">
 <p>
 Incubator policy <a href="/incubation/Incubation_Policy.html#Releases">requires</a> that 
@@ -1458,9 +1382,7 @@ So, it is of particular importance that 
            </ul>
 </div>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="release-guidelines">Release Guidelines</a>
-</h2>
+        <h2 id='release-guidelines'><img src="../images/redarrow.gif" />Release Guidelines</h2>
 <div class="section-content">
 <p>
 In addition to policy, the infrastructure, public relations and legal teams also
@@ -1478,13 +1400,9 @@ lists. Subscribe to:
             <li><em>infrastructure-issues</em> for matters related to </li>
         </ul>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="best-practice">Best Practice</a>
-</h2>
-<div class="section-content">
-<h3>
-   <a name="best-practice-preparation">Preparation</a>
-</h3>
+        <h2 id='best-practice'><img src="../images/redarrow.gif" />Best Practice</h2>
+<div class="section-content">
+<h3 id='best-practice-preparation'>Preparation</h3>
 <div class="section-content">
 <p>
 Preparation is the key to quality. The <a href="#glossary-release-manager">release manager</a>
@@ -1495,9 +1413,7 @@ will need to organise and coordinate thi
 				<li>Check <a href="#best-practice-prepare-documentation">documentation</a></li>
 			</ul>
 </div>
-<h3>
-   <a name="best-practice-bugs">Bugs</a>
-</h3>
+<h3 id='best-practice-bugs'>Bugs</h3>
 <div class="section-content">
 <p>
 The list of open issues needs to be analyzed. The community needs to decide which 
@@ -1512,9 +1428,7 @@ An accurate view of those bugs which are
 to concentrate community effort. Consider asking reporters to donate unit tests.
     		</p>
 </div>
-<h3>
-   <a name="best-practice-prepare-documentation">Preparing Documentation</a>
-</h3>
+<h3 id='best-practice-prepare-documentation'>Preparing Documentation</h3>
 <div class="section-content">
 <p>
 Any documentation that the release contains should be proof-read and spell checked.
@@ -1523,9 +1437,7 @@ So typically, the release manager needs 
 A release is a good time to concentrate energy on documentation.
     		</p>
 </div>
-<h3>
-   <a name="best-practice-jars">Jars</a>
-</h3>
+<h3 id='best-practice-jars'>Jars</h3>
 <div class="section-content">
 <ul>
                 <li><code>META-INF</code>
@@ -1541,18 +1453,14 @@ A release is a good time to concentrate 
                 </li>
             </ul>
 </div>
-<h3>
-   <a name="best-practice-naming">Artifact Naming</a>
-</h3>
+<h3 id='best-practice-naming'>Artifact Naming</h3>
 <div class="section-content">
 <p>
             TODO: should include apache in the title (gives trademark protection against different jars 
             with the same name)
         	</p>
 </div>
-<h3>
-   <a name="best-practice-types">Package Types</a>
-</h3>
+<h3 id='best-practice-types'>Package Types</h3>
 <div class="section-content">
 <p>
  TODO: glossary - distribution type: based on the same tagged source built  
@@ -1569,9 +1477,7 @@ A release is a good time to concentrate 
  This means multiple packages may be shipped as various compressed artifacts (eg tar.gz and .zip).
         	</p>
 </div>
-<h3>
-   <a name="best-practice-downstream">Downstream Packagers</a>
-</h3>
+<h3 id='best-practice-downstream'>Downstream Packagers</h3>
 <div class="section-content">
 <p>
  TODO: glossary - downstream packager: takes an apache release and packages it for a particular platform.
@@ -1583,9 +1489,7 @@ A release is a good time to concentrate 
 TODO: write up gentoo wiki on good upstream. google for other distros.
         	</p>
 </div>
-<h3>
-   <a name="best-practice-source">Source Package</a>
-</h3>
+<h3 id='best-practice-source'>Source Package</h3>
 <div class="section-content">
 <p>
         	TODO: describe what a source package is; version control for source packages; 
@@ -1615,9 +1519,7 @@ prefer to verify and then build their ow
 is easy to create but helps to reach these audiences.
         	</p>
 </div>
-<h3>
-   <a name="best-practice-binary">Binary Package</a>
-</h3>
+<h3 id='best-practice-binary'>Binary Package</h3>
 <div class="section-content">
 <p>
 A binary package is any package that is not an exported snapshot of the source.
@@ -1625,9 +1527,7 @@ Binary packages may include some source 
 For others, it does not.
         	</p>
 </div>
-<h3>
-   <a name="best-practice-documentation">Release Documentation</a>
-</h3>
+<h3 id='best-practice-documentation'>Release Documentation</h3>
 <div class="section-content">
 <p>
 Users expect <a href="#glossary-release-documentation">release documentation</a> 
@@ -1677,9 +1577,7 @@ with each release as adoption grows.
  and in ANNOUNCEMENTSs (TODO add links to this in announcements section)
         	</p>
 </div>
-<h3>
-   <a name="best-practice-status">STATUS document</a>
-</h3>
+<h3 id='best-practice-status'>STATUS document</h3>
 <div class="section-content">
 <p>
 TODO: check this TODO: the STATUS document should be checked to ensure that it is up to date
@@ -1687,9 +1585,7 @@ before release. Incubator releases shoul
 before releasing. The legal STATUS of the code base should be clean before it is released.
         	</p>
 </div>
-<h3>
-   <a name="best-practice-license">LICENSE and NOTICE</a>
-</h3>
+<h3 id='best-practice-license'>LICENSE and NOTICE</h3>
 <div class="section-content">
 <p>
 Apache projects may distribute artifacts and documents as part of a release
@@ -1712,9 +1608,7 @@ belongs in the NOTICE document.  See <a 
 this document</a> for the typical example.
                 </p>
 </div>
-<h3>
-   <a name="best-practice-audit">Legal Audit</a>
-</h3>
+<h3 id='best-practice-audit'>Legal Audit</h3>
 <div class="section-content">
 <p>
  It is of particular importance that released code is clean. 
@@ -1725,9 +1619,7 @@ this document</a> for the typical exampl
  a little time reading again the legal release material. 
         	</p>
 </div>
-<h3>
-   <a name="best-practice-formats">Compression Formats</a>
-</h3>
+<h3 id='best-practice-formats'>Compression Formats</h3>
 <div class="section-content">
 <p>
 <a href="best-practice-packages">Packages</a> of all 
@@ -1784,9 +1676,7 @@ It is recommended that project which do 
 *nix package as a bz2 archive.
             </p>
 </div>
-<h3>
-   <a name="best-practice-source-build">Source Package Build</a>
-</h3>
+<h3 id='best-practice-source-build'>Source Package Build</h3>
 <div class="section-content">
 <p>
 This section applies only to compiled languages.
@@ -1800,9 +1690,7 @@ TODO: best practices for instructing use
 Build instructions should give supported version numbers for build tools (for example, maven and ant).
             </p>
 </div>
-<h3>
-   <a name="best-practice-dependencies">Dependencies</a>
-</h3>
+<h3 id='best-practice-dependencies'>Dependencies</h3>
 <div class="section-content">
 <p>
 TODO: information about dependencies is a FAQ. releases should indicate dependencies
@@ -1829,9 +1717,7 @@ the correct versions. Note that this inc
 dependencies.
         	</p>
 </div>
-<h3>
-   <a name="best-practice-distributing-libraries">Distributing Libraries</a>
-</h3>
+<h3 id='best-practice-distributing-libraries'>Distributing Libraries</h3>
 <div class="section-content">
 <p>
 TODO: ASF policy compliance
@@ -1841,9 +1727,7 @@ TODO: project policy - explicit policy s
 TODO: Discussion on the merits of distributing dependent jars. This should be a link to the notes section
             </p>
 </div>
-<h3>
-   <a name="best-practice-notice">NOTICE files</a>
-</h3>
+<h3 id='best-practice-notice'>NOTICE files</h3>
 <div class="section-content">
 <p>
 Read <a href="http://apache.org/legal/src-headers.html#notice">this</a>.
@@ -1879,9 +1763,7 @@ The exact name may be optionally suffixe
 and <code>NOTICE.txt</code> are fine.
             </p>
 </div>
-<h3>
-   <a name="best-practices-svn">Subversion Best Practices</a>
-</h3>
+<h3 id='best-practices-svn'>Subversion Best Practices</h3>
 <div class="section-content">
 <p>
         	TODO: svn is flexible. branches and tags with svn are not the same as with cvs.
@@ -1907,9 +1789,7 @@ This ensure that all the source for the 
 changes then the release will no longer be complete reproducible.
         	</p>
 </div>
-<h3>
-   <a name="best-practice-reproducability">Reproducibility</a>
-</h3>
+<h3 id='best-practice-reproducability'>Reproducibility</h3>
 <div class="section-content">
 <p>
 It is important that any release can be reproduced from the source at any time in the future. 
@@ -1929,9 +1809,7 @@ The requirements of the build should be 
 and platforms used to build the release should be noted.
         	</p>
 </div>
-<h3>
-   <a name="best-practice-release-as-advertising">Release As Advertising</a>
-</h3>
+<h3 id='best-practice-release-as-advertising'>Release As Advertising</h3>
 <div class="section-content">
 <p>
 Releases are a primary form of communication with open source users and potential developers.
@@ -1940,9 +1818,7 @@ TODO: link into media relations and anno
 on new features, freshmeat, downstream packagers)
         	</p>
 </div>
-<h3>
-   <a name="best-practice-dependencies">Dependencies</a>
-</h3>
+<h3 id='best-practice-dependencies'>Dependencies</h3>
 <div class="section-content">
 <p>
 As well as libraries, projects often have more subtle dependencies.
@@ -1965,9 +1841,7 @@ If any dependencies are cryptographic li
 to fill in some <a href="TODO:">paperwork</a>. 
         	</p>
 </div>
-<h3>
-   <a name="announcements">Announcements</a>
-</h3>
+<h3 id='announcements'>Announcements</h3>
 <div class="section-content">
 <p>
 TODO: release managers should ensure that releases are announced.
@@ -1985,9 +1859,7 @@ Announcements should be posted from the 
 <code>apache.org</code> address.
         	</p>
 </div>
-<h3>
-   <a name="best-practice-incubator-release-vote">Incubator Release Vote</a>
-</h3>
+<h3 id='best-practice-incubator-release-vote'>Incubator Release Vote</h3>
 <div class="section-content">
 <p>
 All releases by podlings must be approved by the TODO: link Incubator PMC. The conventional process
@@ -2003,9 +1875,7 @@ The release manager should post the call
                 <li>Link to the tag from which the release is cut</li>
             </ul>
 </div>
-<h3>
-   <a name="best-practice-mailing-lists"></a>
-</h3>
+<h3 id='best-practice-mailing-lists'></h3>
 <div class="section-content">
 <p>
 Release managers should subscribe to a number of Apache-wide mailing lists.
@@ -2021,9 +1891,7 @@ managers ensure that they keep up to dat
 Release managers for incubating podlings should also subscribe to the TODO: link general list.
             </p>
 </div>
-<h3>
-   <a name="best-practices-release-candidates">Release Candidates</a>
-</h3>
+<h3 id='best-practices-release-candidates'>Release Candidates</h3>
 <div class="section-content">
 <p>
 A release candidate is a set of artifacts upon which a vote is held for a release.
@@ -2061,9 +1929,7 @@ release candidates. TODO:link to dev ins
 Please remember to delete release candidates after voting concludes.
         	</p>
 </div>
-<h3>
-   <a name="signing-releases">Signatures</a>
-</h3>
+<h3 id='signing-releases'>Signatures</h3>
 <div class="section-content">
 <p>
  TODO: links to release signing documentation
@@ -2077,9 +1943,7 @@ Please remember to delete release candid
  isolated installation to store the code signing key and to sign releases.
         	</p>
 </div>
-<h3>
-   <a name="best-practice-maven">Maven</a>
-</h3>
+<h3 id='best-practice-maven'>Maven</h3>
 <div class="section-content">
 <p>
 <a href="http://maven.apache.org">Apache Maven</a> is a tool used by many podlings.
@@ -2101,13 +1965,9 @@ For example
 </pre></code>
 </div>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="notes">Notes</a>
-</h2>
-<div class="section-content">
-<h3>
-   <a name="notes-on-licenses">License Issues</a>
-</h3>
+        <h2 id='notes'><img src="../images/redarrow.gif" />Notes</h2>
+<div class="section-content">
+<h3 id='notes-on-licenses'>License Issues</h3>
 <div class="section-content">
 <p>
             TODO: content
@@ -2118,9 +1978,7 @@ a CLA or CCLA
 TODO: complete content
             </p>
 </div>
-<h3>
-   <a name="notes-disclaimer">The Incubator Disclaimer</a>
-</h3>
+<h3 id='notes-disclaimer'>The Incubator Disclaimer</h3>
 <div class="section-content">
 <p>
             TODO: the incubator requires that users are informed that the by
@@ -2128,9 +1986,7 @@ TODO: complete content
             DISCLAIMER. It is recommended that it is not included in NOTICES
             </p>
 </div>
-<h3>
-   <a name="distributing-jars">Distributing Jars</a>
-</h3>
+<h3 id='distributing-jars'>Distributing Jars</h3>
 <div class="section-content">
 <p>
             TODO: link to infrastructure
@@ -2145,9 +2001,7 @@ It is convenient to include these with t
 either with Ant or Maven. TODO: move examples here from jakarta commons releases.
             </p>
 </div>
-<h3>
-   <a name="jar-manifest">Jar MANIFEST</a>
-</h3>
+<h3 id='jar-manifest'>Jar MANIFEST</h3>
 <div class="section-content">
 <p>
 TODO
@@ -2169,17 +2023,13 @@ It does not, by default, include some re
 so that it includes the missing recommended entries.
             </p>
 </div>
-<h3>
-   <a name="best-practice-release-candidate">Release Candidates</a>
-</h3>
+<h3 id='best-practice-release-candidate'>Release Candidates</h3>
 <div class="section-content">
 <p>
 There are two distinct approaches: <a href="#glossary-release-candidate">release candidate</a> and TODO.  
         	</p>
 </div>
-<h3>
-   <a name="best-practice-versioning">Versioning</a>
-</h3>
+<h3 id='best-practice-versioning'>Versioning</h3>
 <div class="section-content">
 <p>
 There are several good versioning strategies used by projects at Apache. The version strategy
@@ -2218,9 +2068,7 @@ A project should therefore use their own
  but whose code is solid for those features which are implemented.
         	</p>
 </div>
-<h3>
-   <a name="notes-numbering-between-releases">Version Numbering Between Releases</a>
-</h3>
+<h3 id='notes-numbering-between-releases'>Version Numbering Between Releases</h3>
 <div class="section-content">
 <p>
 It is useful to use a system of versioning for development (non-release) version numbers that
@@ -2242,9 +2090,7 @@ after cutting <code>apache-foo-1.5.6</co
 <code>1.6</code>. 
         	</p>
 </div>
-<h3>
-   <a name="best-practice-unique-names">Unique Artifact Names</a>
-</h3>
+<h3 id='best-practice-unique-names'>Unique Artifact Names</h3>
 <div class="section-content">
 <p>
  Every <a href="glossay-artifact">artifact</a> distributed should have a name that is unique.
@@ -2267,9 +2113,7 @@ by the usual file type suffix.
 So, the traditional format is apache-project-product-type-version.format.
         	</p>
 </div>
-<h3>
-   <a name="release-notes">Release Notes</a>
-</h3>
+<h3 id='release-notes'>Release Notes</h3>
 <div class="section-content">
 <p>
 TODO: rewrite this is section distinguishing between the content and the presentation.
@@ -2362,9 +2206,7 @@ This may be included by reference to the
 but (for the benefit of those that don't read document) should be mentioned.
 			</p>
 </div>
-<h3>
-   <a name="note-compatibility-checkers">Compatibility Checkers</a>
-</h3>
+<h3 id='note-compatibility-checkers'>Compatibility Checkers</h3>
 <div class="section-content">
 <p>
 Some tools used by Apache projects:
@@ -2378,9 +2220,7 @@ Some tools used by Apache projects:
 				</li>
 			</ul>
 </div>
-<h3>
-   <a name="notes-change-log">Change Logs</a>
-</h3>
+<h3 id='notes-change-log'>Change Logs</h3>
 <div class="section-content">
 <p>
 TODO: should this be in best practices
@@ -2403,9 +2243,7 @@ The change log typically includes every 
 the last release.
         	</p>
 </div>
-<h3>
-   <a name="notes-signing-releases">Signing Releases</a>
-</h3>
+<h3 id='notes-signing-releases'>Signing Releases</h3>
 <div class="section-content">
 <p>
 TODO: links to dev pages
@@ -2436,18 +2274,14 @@ learnt in a short time. TODO: link to fo
  release managers knows whether a signature is their own.
         	</p>
 </div>
-<h3>
-   <a name="note-on-multiple-products">On Multiple Products</a>
-</h3>
+<h3 id='note-on-multiple-products'>On Multiple Products</h3>
 <div class="section-content">
 <p>
 A project may release a number of distinct products created by the same community.
 TODO: differences between products and packages.
         	</p>
 </div>
-<h3>
-   <a name="notes-on-templates">On Template Sources</a>
-</h3>
+<h3 id='notes-on-templates'>On Template Sources</h3>
 <div class="section-content">
 <p>
         	TODO: this is probably a best practice
@@ -2469,9 +2303,7 @@ If not then consider adding a NOTE or a 
 than a license header.
         	</p>
 </div>
-<h3>
-   <a name="notes-on-java-version">On Java Versions</a>
-</h3>
+<h3 id='notes-on-java-version'>On Java Versions</h3>
 <div class="section-content">
 <p>
 Indicating supported versions for dependencies is 
@@ -2509,22 +2341,16 @@ the appropriate version of the Java API.
 placed.
         	</p>
 </div>
-<h3>
-   <a name="notes-on-export-regulations">On Export Regulations</a>
-</h3>
+<h3 id='notes-on-export-regulations'>On Export Regulations</h3>
 <div class="section-content">
 <p>
 TODO preamble TODO link to legal
         	</p>
 </div>
-<h3>
-   <a name="notes-on-compression-formats"></a>
-</h3>
+<h3 id='notes-on-compression-formats'></h3>
 <div class="section-content">
 </div>
-<h3>
-   <a name="notes-on-line-endings">On Line Endings</a>
-</h3>
+<h3 id='notes-on-line-endings'>On Line Endings</h3>
 <div class="section-content">
 <p>
 It is convenient for users and more consistent if line endings for appropriate files
@@ -2538,9 +2364,7 @@ build with <a href="http://ant.apace.org
 <a href="http://ant.apache.org/manual/CoreTasks/fixcrlf.html">fixcrlf</a>.
             </p>
 </div>
-<h3>
-   <a name="notes-press-releases">On Press Releases</a>
-</h3>
+<h3 id='notes-press-releases'>On Press Releases</h3>
 <div class="section-content">
 <p>
 It is rare for Apache projects to issue mainstream press releases 
@@ -2551,9 +2375,7 @@ press interest in a release then please 
 TODO: link to public relations committee
         	</p>
 </div>
-<h3>
-   <a name="notes-on-signing-jars">On Signing Jars</a>
-</h3>
+<h3 id='notes-on-signing-jars'>On Signing Jars</h3>
 <div class="section-content">
 <p>
 Java includes a standard mechanism for signing jars. Apache uses digital
@@ -2567,9 +2389,7 @@ sealed against modification. Open source
 TODO: rephrase and check
         	</p>
 </div>
-<h3>
-   <a name="notes-license-headers">On License Headers</a>
-</h3>
+<h3 id='notes-license-headers'>On License Headers</h3>
 <div class="section-content">
 <p>
             TODO: links into legal documentation. discuss issues about which files need to apply.
@@ -2597,9 +2417,7 @@ TODO: check with legal-discuss then move
 TODO: link into provenance
 			</p>
 </div>
-<h3>
-   <a name="code-provenance">Code Provenance</a>
-</h3>
+<h3 id='code-provenance'>Code Provenance</h3>
 <div class="section-content">
 <p>
 <a href="LINK">License headers</a> may seem trivial and to some extent that is true. 
@@ -2629,17 +2447,13 @@ by including a short header if the file 
 in the directory containing license information. This makes code auditing much easier.
 			</p>
 </div>
-<h3>
-   <a name="note-standards">Implementations Of Standards</a>
-</h3>
+<h3 id='note-standards'>Implementations Of Standards</h3>
 <div class="section-content">
 <p>
 TODO: importance of accurately reporting to the user the state of an implementation
 TODO: importance of complying with the reporting requirements set by the standard creator
         	</p>
-<h4>
-   <a name="notes-jsr">JSRs</a>
-</h4>
+<h4 id='notes-jsr'>JSRs</h4>
 <div class="section-content">
 <p>
 TODO: write up http://marc.theaimsgroup.com/?l=incubator-general&amp;m=116577422312412&amp;w=2
@@ -2647,9 +2461,7 @@ TODO: then check with Geir
         		</p>
 </div>
 </div>
-<h3>
-   <a name="note-license-and-notice">Understanding Content For NOTICE and LICENSE</a>
-</h3>
+<h3 id='note-license-and-notice'>Understanding Content For NOTICE and LICENSE</h3>
 <div class="section-content">
 <p>
 
@@ -2713,9 +2525,7 @@ It is better to include any other types 
 in the RELEASE-NOTES or in a README.
         	</p>
 </div>
-<h3>
-   <a name="note-votes">VOTEs</a>
-</h3>
+<h3 id='note-votes'>VOTEs</h3>
 <div class="section-content">
 <p>
         	TODO: add bill's excellent quote (apologies for the pun)
@@ -2774,9 +2584,7 @@ is retained but also makes it clear that
 TODO: move VOTE netiquette into either ppmc or lists and link from here
 TODO: this has turned into best practice.
         	</p>
-<h4>
-   <a name="note-pmc-vote"></a>
-</h4>
+<h4 id='note-pmc-vote'></h4>
 <div class="section-content">
 <p>
 Each release requires a positive vote binding on Apache. This means
@@ -2790,9 +2598,7 @@ votes on the general list.
         		</p>
 </div>
 </div>
-<h3>
-   <a name="notes-revote">On Managing VOTE Threads</a>
-</h3>
+<h3 id='notes-revote'>On Managing VOTE Threads</h3>
 <div class="section-content">
 <p>
         	TODO: consider whether this would be better moved elsewhere
@@ -2822,9 +2628,7 @@ This allows people to check their votes 
  release candidate).
         	</p>
 </div>
-<h3>
-   <a name="notes-release-candidate-java">On Java Release Candidates</a>
-</h3>
+<h3 id='notes-release-candidate-java'>On Java Release Candidates</h3>
 <div class="section-content">
 <p>
 This section applies to any package that contains re-distributable artifacts which contain version
@@ -2841,9 +2645,7 @@ uniquely named. Uncertainty about exact 
 issues in the past.
 			</p>
 </div>
-<h3>
-   <a name="notes-on-gnu-tar">GNU Tar Known Incompatibilities</a>
-</h3>
+<h3 id='notes-on-gnu-tar'>GNU Tar Known Incompatibilities</h3>
 <div class="section-content">
 <p>
 Typically, applications used to create <code>tar.gz</code> files are based on
@@ -2852,9 +2654,7 @@ GNU tar. Unfortunately, the tar which sh
         	TODO: check information and expand
         	</p>
 </div>
-<h3>
-   <a name="notes-on-source-only-releases">On Source-Only Releases</a>
-</h3>
+<h3 id='notes-on-source-only-releases'>On Source-Only Releases</h3>
 <div class="section-content">
 <p>
 A source-only release contains only the source package. Though users often prefer
@@ -2864,9 +2664,7 @@ and fixing bugs. Occasionally, projects 
 the software via a downstream repackage may prefer to release source only.
         	</p>
 </div>
-<h3>
-   <a name="notes-on-binary-only-releases">On Binary-Only Releases</a>
-</h3>
+<h3 id='notes-on-binary-only-releases'>On Binary-Only Releases</h3>
 <div class="section-content">
 <p>
 Releases containing only binary packages are not performed at The Apache Software Foundation.
@@ -2877,13 +2675,9 @@ project needs to recruit new developers 
         	</p>
 </div>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="glossary">Glossary</a>
-</h2>
-<div class="section-content">
-<h3>
-   <a name="glossary-cla">Contributor License Agreement</a>
-</h3>
+        <h2 id='glossary'><img src="../images/redarrow.gif" />Glossary</h2>
+<div class="section-content">
+<h3 id='glossary-cla'>Contributor License Agreement</h3>
 <div class="section-content">
 <p>
  A Contributor License Agreement (CLA) is a contract between a contributor
@@ -2903,9 +2697,7 @@ See
                 </li>
             </ul>
 </div>
-<h3>
-   <a name="glossary-ccla">Contributor License Agreement - Corporate</a>
-</h3>
+<h3 id='glossary-ccla'>Contributor License Agreement - Corporate</h3>
 <div class="section-content">
 <p>
  A Corporate Contributor License Agreement (CCLA) is a contract between a corporation
@@ -2927,9 +2719,7 @@ See
                 </li>
             </ul>
 </div>
-<h3>
-   <a name="glossary-artifact">Distributed Artifact</a>
-</h3>
+<h3 id='glossary-artifact'>Distributed Artifact</h3>
 <div class="section-content">
 <p>
 A file that is actually made available for download.  Note this does <strong>NOT</strong> imply
@@ -2942,34 +2732,26 @@ are only intended for people participati
             TODO (include link to infra documentation)
             </p>
 </div>
-<h3>
-   <a name="glossary-license">LICENSE file</a>
-</h3>
+<h3 id='glossary-license'>LICENSE file</h3>
 <div class="section-content">
 <p>
   Document containing the licenses for the package.
         	</p>
 </div>
-<h3>
-   <a name="glossary-notice">NOTICE file</a>
-</h3>
+<h3 id='glossary-notice'>NOTICE file</h3>
 <div class="section-content">
 <p>
   Document containing additional required copyright and attribute information.
             </p>
 </div>
-<h3>
-   <a name="glossary-ceremony">Ceremony</a>
-</h3>
+<h3 id='glossary-ceremony'>Ceremony</h3>
 <div class="section-content">
 <p>
         	Process and procedure associated with - but not necessary to - a particular end.
         	TODO: link to foundation docs
         	</p>
 </div>
-<h3>
-   <a name="glossary-manifest">Jar MANIFEST</a>
-</h3>
+<h3 id='glossary-manifest'>Jar MANIFEST</h3>
 <div class="section-content">
 <p>
 Meta data, enumerating the contents of the Jar, associated with the Java Jar format.
@@ -2978,9 +2760,7 @@ Meta data, enumerating the contents of t
             TODO link to sun documentation
             </p>
 </div>
-<h3>
-   <a name="glossary-license-header">License Header</a>
-</h3>
+<h3 id='glossary-license-header'>License Header</h3>
 <div class="section-content">
 <p>
 Text referring to the license for a file (as opposed to the license text).
@@ -2989,9 +2769,7 @@ Text referring to the license for a file
             TODO (include link to legal documentation)
             </p>
 </div>
-<h3>
-   <a name="glossary-release-manager">Release Manager</a>
-</h3>
+<h3 id='glossary-release-manager'>Release Manager</h3>
 <div class="section-content">
 <p>
 Committer responsible for shepherding the release.  This role is rather time consuming
@@ -3040,18 +2818,14 @@ maven central if appropriate, and announ
             cuts the release) and the social one (who organizes it).
             </p>
 </div>
-<h3>
-   <a name="glossary-release-candidate">Release Candidate</a>
-</h3>
+<h3 id='glossary-release-candidate'>Release Candidate</h3>
 <div class="section-content">
 <p>
 Collection of artifacts to be tested and voted on in order to release them.  Sometimes
 folks use this term to refer only to a candidate source package.
             </p>
 </div>
-<h3>
-   <a name="glossary-package">Package</a>
-</h3>
+<h3 id='glossary-package'>Package</h3>
 <div class="section-content">
 <p>
         A file created from a project's source code with the intent to distribute.  Note
@@ -3061,26 +2835,20 @@ folks use this term to refer only to a c
         Here we use it in the generic sense to refer to software packages.
             </p>
 </div>
-<h3>
-   <a name="glossary-artifact">Artifact</a>
-</h3>
+<h3 id='glossary-artifact'>Artifact</h3>
 <div class="section-content">
 <p>
             Artifact is a generic term for a package, or more generally a file of any kind.
             </p>
 </div>
-<h3>
-   <a name="glossary-package-type">Package Type</a>
-</h3>
+<h3 id='glossary-package-type'>Package Type</h3>
 <div class="section-content">
 <p>
 Packages are typically either source packages or binary packages (i.e. builds).
 Sometimes separate documentation packages are released alongside the source package.
             </p>
 </div>
-<h3>
-   <a name="glossary-source-package">Source Package</a>
-</h3>
+<h3 id='glossary-source-package'>Source Package</h3>
 <div class="section-content">
 <p>
 A source package is typically a compressed archive file containing a 
@@ -3088,18 +2856,14 @@ simple export from the repository, optio
 scripts run on it.
             </p>
 </div>
-<h3>
-   <a name="glossary-binary-package">Binary Package</a>
-</h3>
+<h3 id='glossary-binary-package'>Binary Package</h3>
 <div class="section-content">
 <p>
 Binary packages are typically platform-specific builds of the source package.
 There is only one canonical source package but there may be several binary packages.
             </p>
 </div>
-<h3>
-   <a name="glossary-cutting-release">Cutting The Release</a>
-</h3>
+<h3 id='glossary-cutting-release'>Cutting The Release</h3>
 <div class="section-content">
 <p>
 The actual execution of the release. Typically consists of building the packages
@@ -3107,9 +2871,7 @@ from the repository tag, along with any 
 TODO: link to infra
         	</p>
 </div>
-<h3>
-   <a name="glossary-guidelines">Guidelines</a>
-</h3>
+<h3 id='glossary-guidelines'>Guidelines</h3>
 <div class="section-content">
 <p>
 Guidelines are documented recommendations which have not yet been blessed as policy.
@@ -3117,9 +2879,7 @@ There are usually good reasons why proje
 even if these may be initially obvious.
         	</p>
 </div>
-<h3>
-   <a name="glossary-release-documentation">Release Documentation</a>
-</h3>
+<h3 id='glossary-release-documentation'>Release Documentation</h3>
 <div class="section-content">
 <p>
 Documents a particular release of a product rather than the product itself.
@@ -3127,17 +2887,13 @@ Note that release documentation also occ
 release manager to follow during the process of creating a release.
                 </p>
 </div>
-<h3>
-   <a name="glossary-issue-tracker">Issue Tracking System</a>
-</h3>
+<h3 id='glossary-issue-tracker'>Issue Tracking System</h3>
 <div class="section-content">
 <p>
 An application that store manages issues reported in Apache products. TODO: links
         	</p>
 </div>
-<h3>
-   <a name="glossary-ipmc">Incubator Project Management Committee (Incubator PMC)</a>
-</h3>
+<h3 id='glossary-ipmc'>Incubator Project Management Committee (Incubator PMC)</h3>
 <div class="section-content">
 <p>
  The committee charged by the <a href="http://www.apache.org/foundation/board/">board</a> 
@@ -3158,9 +2914,7 @@ An application that store manages issues
                 </li>
             </ul>
 </div>
-<h3>
-   <a name="glossary-ppmc">Podling Project Management Committee (Podling PMC)</a>
-</h3>
+<h3 id='glossary-ppmc'>Podling Project Management Committee (Podling PMC)</h3>
 <div class="section-content">
 <p>
 The group of committers charged with development and direction of a podling.  Not a formally recognized
@@ -3169,9 +2923,7 @@ the seed for a formal PMC if the project
 Podling PMC members join a pre-existing PMC to continue development as a subproject of that PMC.
             </p>
 </div>
-<h3>
-   <a name="glossary-pmc">Project Management Committee</a>
-</h3>
+<h3 id='glossary-pmc'>Project Management Committee</h3>
 <div class="section-content">
 <p>
  A committee charged by the <a href="http://www.apache.org/foundation/board/">board</a> 
@@ -3189,9 +2941,7 @@ Podling PMC members join a pre-existing 
                 </li>
              </ul>
 </div>
-<h3>
-   <a name="glossary-incubator-dist">Incubator Distribution Directory</a>
-</h3>
+<h3 id='glossary-incubator-dist'>Incubator Distribution Directory</h3>
 <div class="section-content">
 <p>
 All Incubator authorised by the incubator are contained within the
@@ -3202,9 +2952,7 @@ www.apache.org/dist/incubator
 </code>
 </div>
 </div>
-<h3>
-   <a name="glossary-podling-dist">Podling Distribution Directory</a>
-</h3>
+<h3 id='glossary-podling-dist'>Podling Distribution Directory</h3>
 <div class="section-content">
 <p>
 All releases created by a podling are contained within a sub-directory of the

Modified: incubator/public/trunk/site-publish/guides/releasing-eclipse-update-site.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/releasing-eclipse-update-site.html?rev=1182994&r1=1182993&r2=1182994&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/releasing-eclipse-update-site.html [utf-8] (original)
+++ incubator/public/trunk/site-publish/guides/releasing-eclipse-update-site.html [utf-8] Thu Oct 13 17:17:19 2011
@@ -48,49 +48,49 @@
      <input name="Search" value="Go" type="submit"/>
     </form>
           <div class="menuheader"><a 
-href="/projects/index.html">Incubator Projects</a></div> 
+href="../projects/index.html">Incubator Projects</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
 href="http://www.apache.org/foundation/glossary.html#Podling">Podlings (What's that?)</a></div> 
     <menu compact="compact">
-          <li><a href="/incubation/Incubation_Policy.html">How? (Policy)</a></li> 
-          <li><a href="/incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li> 
-          <li><a href="/incubation/Process_Description.html">When? (Process)</a></li> 
+          <li><a href="../incubation/Incubation_Policy.html">How? (Policy)</a></li> 
+          <li><a href="../incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li> 
+          <li><a href="../incubation/Process_Description.html">When? (Process)</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/guides/index.html">Entry Guides</a></div> 
+href="../guides/index.html">Entry Guides</a></div> 
     <menu compact="compact">
-          <li><a href="/guides/proposal.html">Proposal Guide</a></li> 
+          <li><a href="../guides/proposal.html">Proposal Guide</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/guides/index.html">Podling Guides</a></div> 
+href="../guides/index.html">Podling Guides</a></div> 
     <menu compact="compact">
-          <li><a href="/guides/committer.html">Podling Committers</a></li> 
-          <li><a href="/guides/ppmc.html">Podling PMC (PPMC)</a></li> 
-          <li><a href="/guides/mentor.html">Podling Mentor</a></li> 
-          <li><a href="/guides/releasemanagement.html">Podling Releases</a></li> 
-          <li><a href="/guides/branding.html">Podling Branding/Publicity</a></li> 
-          <li><a href="/guides/sites.html">Podling Websites</a></li> 
-          <li><a href="/guides/graduation.html">Graduation</a></li> 
-          <li><a href="/guides/retirement.html">Retirement</a></li> 
+          <li><a href="../guides/committer.html">Podling Committers</a></li> 
+          <li><a href="../guides/ppmc.html">Podling PMC (PPMC)</a></li> 
+          <li><a href="../guides/mentor.html">Podling Mentor</a></li> 
+          <li><a href="../guides/releasemanagement.html">Podling Releases</a></li> 
+          <li><a href="../guides/branding.html">Podling Branding/Publicity</a></li> 
+          <li><a href="../guides/sites.html">Podling Websites</a></li> 
+          <li><a href="../guides/graduation.html">Graduation</a></li> 
+          <li><a href="../guides/retirement.html">Retirement</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/clutch.html">Status of the Clutch</a></div> 
+href="../clutch.html">Status of the Clutch</a></div> 
     <menu compact="compact">
-          <li><a href="/clutch.html">Current Podling Status</a></li> 
-          <li><a href="/clutch.html#steps">Assist with Steps</a></li> 
+          <li><a href="../clutch.html">Current Podling Status</a></li> 
+          <li><a href="../clutch.html#steps">Assist with Steps</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/ip-clearance/index.html">IP Clearance</a></div> 
+href="../ip-clearance/index.html">IP Clearance</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
-href="/whoweare.html">Who We Are</a></div> 
+href="../whoweare.html">Who We Are</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
-href="/sitemap.html">Site Map</a></div> 
+href="../sitemap.html">Site Map</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
@@ -104,11 +104,11 @@ href="http://www.apache.org">ASF</a></di
             </menu>
       <div class="menuheader">Other Guides</div>
     <menu compact="compact">
-          <li><a href="/guides/participation.html">Participation</a></li> 
-          <li><a href="/faq.html">General FAQ</a></li> 
-          <li><a href="/guides/pmc.html">PMC</a> (<a href="/guides/chair.html">Chair</a>)</li> 
-          <li><a href="/guides/lists.html">Mailing Lists</a></li> 
-          <li><a href="/guides/website.html">Incubator Website</a></li> 
+          <li><a href="../guides/participation.html">Participation</a></li> 
+          <li><a href="../faq.html">General FAQ</a></li> 
+          <li><a href="../guides/pmc.html">PMC</a> (<a href="../guides/chair.html">Chair</a>)</li> 
+          <li><a href="../guides/lists.html">Mailing Lists</a></li> 
+          <li><a href="../guides/website.html">Incubator Website</a></li> 
             </menu>
       <div class="menuheader"><a 
 href="http://wiki.apache.org/incubator">Incubator Wiki</a></div> 
@@ -122,13 +122,9 @@ href="http://wiki.apache.org/incubator">
    </div>
    
    <div class="span12">
-            <h2><img src="../images/redarrow.gif" />
-   <a name="intro">A Guide To Releasing Eclipse Update Sites during Incubation (DRAFT)</a>
-</h2>
+            <h2 id='intro'><img src="../images/redarrow.gif" />A Guide To Releasing Eclipse Update Sites during Incubation (DRAFT)</h2>
 <div class="section-content">
-<h3>
-   <a name="TOC">Contents</a>
-</h3>
+<h3 id='TOC'>Contents</h3>
 <div class="section-content">
 <ul>
 <li><a href='#intro'>
@@ -171,18 +167,14 @@ Help Wanted!
 </li>
 </ul>
 </div>
-<h3>
-   <a name="status">Status - DRAFT</a>
-</h3>
+<h3 id='status'>Status - DRAFT</h3>
 <div class="section-content">
 <p>
 This document is under active <a href="#help-wanted">development</a>. This is a first 
 draft intended to allow public review. 
         </p>
 </div>
-<h3>
-   <a name="abstract">Abstract</a>
-</h3>
+<h3 id='abstract'>Abstract</h3>
 <div class="section-content">
 <p> This document is descriptive, not normative. 
           It aims to guide podlings through the process of 
@@ -206,9 +198,7 @@ draft intended to allow public review. 
           This guide describes a process for accomplishing this.
         </p>
 </div>
-<h3>
-   <a name="setting-up-eclipse-mirroring">Setting up Eclipse mirroring</a>
-</h3>
+<h3 id='setting-up-eclipse-mirroring'>Setting up Eclipse mirroring</h3>
 <div class="section-content">
 <p>The Eclipse &lt;site&gt; information will contain a URL that Eclipse uses to get the
         list of mirrors.  To set this up to use the automatic Apache mirroring system, 
@@ -244,9 +234,7 @@ label="Recommended mirror: [preferred]"/
 <p>Doing this will return the list of mirrors to Eclipse, as generated by
         the apache mirroring system</p>
 </div>
-<h3>
-   <a name="update-site-project">Creating and maintaining an Eclipse update site project</a>
-</h3>
+<h3 id='update-site-project'>Creating and maintaining an Eclipse update site project</h3>
 <div class="section-content">
 <p>
           Your project will be making many releases.  Some subset (or perhaps all) of the
@@ -288,9 +276,7 @@ label="Recommended mirror: [preferred]"/
           </li>
         </ul></p>
 </div>
-<h3>
-   <a name="optimized-sites">Optimized update sites</a>
-</h3>
+<h3 id='optimized-sites'>Optimized update sites</h3>
 <div class="section-content">
 <p>Starting with Eclipse 3.3, an optimized form of update sites is possible, through two
         forms of optimization.  One is making use of the pack200 Jar optimizations, part of
@@ -300,9 +286,7 @@ label="Recommended mirror: [preferred]"/
           Update Site Optimization</a> article for details on creating optimized update sites.
         </p>
 </div>
-<h3>
-   <a name="sample-build-process">Sample build process</a>
-</h3>
+<h3 id='sample-build-process'>Sample build process</h3>
 <div class="section-content">
 <p>A typical build script builds feature Jars from associated Eclipse feature projects,
         copies (perhaps from Maven repositories to insure getting a particular release level)
@@ -314,9 +298,7 @@ label="Recommended mirror: [preferred]"/
           signEclipseUpdateSite.sh script. 
         </p>
 </div>
-<h3>
-   <a name="help-wanted">Help Wanted!</a>
-</h3>
+<h3 id='help-wanted'>Help Wanted!</h3>
 <div class="section-content">
 <p>Help to improve the system by posting a patch for this document to the
            <a href="https://issues.apache.org/jira/browse/INCUBATOR">incubator section</a> 

Modified: incubator/public/trunk/site-publish/guides/retirement.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/retirement.html?rev=1182994&r1=1182993&r2=1182994&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/retirement.html [utf-8] (original)
+++ incubator/public/trunk/site-publish/guides/retirement.html [utf-8] Thu Oct 13 17:17:19 2011
@@ -48,49 +48,49 @@
      <input name="Search" value="Go" type="submit"/>
     </form>
           <div class="menuheader"><a 
-href="/projects/index.html">Incubator Projects</a></div> 
+href="../projects/index.html">Incubator Projects</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
 href="http://www.apache.org/foundation/glossary.html#Podling">Podlings (What's that?)</a></div> 
     <menu compact="compact">
-          <li><a href="/incubation/Incubation_Policy.html">How? (Policy)</a></li> 
-          <li><a href="/incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li> 
-          <li><a href="/incubation/Process_Description.html">When? (Process)</a></li> 
+          <li><a href="../incubation/Incubation_Policy.html">How? (Policy)</a></li> 
+          <li><a href="../incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li> 
+          <li><a href="../incubation/Process_Description.html">When? (Process)</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/guides/index.html">Entry Guides</a></div> 
+href="../guides/index.html">Entry Guides</a></div> 
     <menu compact="compact">
-          <li><a href="/guides/proposal.html">Proposal Guide</a></li> 
+          <li><a href="../guides/proposal.html">Proposal Guide</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/guides/index.html">Podling Guides</a></div> 
+href="../guides/index.html">Podling Guides</a></div> 
     <menu compact="compact">
-          <li><a href="/guides/committer.html">Podling Committers</a></li> 
-          <li><a href="/guides/ppmc.html">Podling PMC (PPMC)</a></li> 
-          <li><a href="/guides/mentor.html">Podling Mentor</a></li> 
-          <li><a href="/guides/releasemanagement.html">Podling Releases</a></li> 
-          <li><a href="/guides/branding.html">Podling Branding/Publicity</a></li> 
-          <li><a href="/guides/sites.html">Podling Websites</a></li> 
-          <li><a href="/guides/graduation.html">Graduation</a></li> 
-          <li><a href="/guides/retirement.html">Retirement</a></li> 
+          <li><a href="../guides/committer.html">Podling Committers</a></li> 
+          <li><a href="../guides/ppmc.html">Podling PMC (PPMC)</a></li> 
+          <li><a href="../guides/mentor.html">Podling Mentor</a></li> 
+          <li><a href="../guides/releasemanagement.html">Podling Releases</a></li> 
+          <li><a href="../guides/branding.html">Podling Branding/Publicity</a></li> 
+          <li><a href="../guides/sites.html">Podling Websites</a></li> 
+          <li><a href="../guides/graduation.html">Graduation</a></li> 
+          <li><a href="../guides/retirement.html">Retirement</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/clutch.html">Status of the Clutch</a></div> 
+href="../clutch.html">Status of the Clutch</a></div> 
     <menu compact="compact">
-          <li><a href="/clutch.html">Current Podling Status</a></li> 
-          <li><a href="/clutch.html#steps">Assist with Steps</a></li> 
+          <li><a href="../clutch.html">Current Podling Status</a></li> 
+          <li><a href="../clutch.html#steps">Assist with Steps</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/ip-clearance/index.html">IP Clearance</a></div> 
+href="../ip-clearance/index.html">IP Clearance</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
-href="/whoweare.html">Who We Are</a></div> 
+href="../whoweare.html">Who We Are</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
-href="/sitemap.html">Site Map</a></div> 
+href="../sitemap.html">Site Map</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
@@ -104,11 +104,11 @@ href="http://www.apache.org">ASF</a></di
             </menu>
       <div class="menuheader">Other Guides</div>
     <menu compact="compact">
-          <li><a href="/guides/participation.html">Participation</a></li> 
-          <li><a href="/faq.html">General FAQ</a></li> 
-          <li><a href="/guides/pmc.html">PMC</a> (<a href="/guides/chair.html">Chair</a>)</li> 
-          <li><a href="/guides/lists.html">Mailing Lists</a></li> 
-          <li><a href="/guides/website.html">Incubator Website</a></li> 
+          <li><a href="../guides/participation.html">Participation</a></li> 
+          <li><a href="../faq.html">General FAQ</a></li> 
+          <li><a href="../guides/pmc.html">PMC</a> (<a href="../guides/chair.html">Chair</a>)</li> 
+          <li><a href="../guides/lists.html">Mailing Lists</a></li> 
+          <li><a href="../guides/website.html">Incubator Website</a></li> 
             </menu>
       <div class="menuheader"><a 
 href="http://wiki.apache.org/incubator">Incubator Wiki</a></div> 
@@ -122,22 +122,16 @@ href="http://wiki.apache.org/incubator">
    </div>
    
    <div class="span12">
-            <h2><img src="../images/redarrow.gif" />
-   <a name="preamble">Guide to Retirement</a>
-</h2>
+            <h2 id='preamble'><img src="../images/redarrow.gif" />Guide to Retirement</h2>
 <div class="section-content">
-<h3>
-   <a name="abstract">Abstract</a>
-</h3>
+<h3 id='abstract'>Abstract</h3>
 <div class="section-content">
 <p>
 					The intent of this document is to help mentors to understand the process of retirement.
 				</p>
 </div>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="introduction">What is Retirement?</a>
-</h2>
+        <h2 id='introduction'><img src="../images/redarrow.gif" />What is Retirement?</h2>
 <div class="section-content">
 <p>
 				A retired project is a project which has been closed down by the PPMC or by the IPMC for various reasons.
@@ -156,9 +150,7 @@ href="http://wiki.apache.org/incubator">
 				In some cases the developers of a project might be opposed to retirement, while the IPMC is in favour because
 				its members cannot see a succesfull graduation now or in future. In this case the IPMC decides about the retirement. 
 			</p>
-<h3>
-   <a name="steps-to-retirement">Steps to retirement</a>
-</h3>
+<h3 id='steps-to-retirement'>Steps to retirement</h3>
 <div class="section-content">
 <p>
 					Follow the following steps to retire a project:		

Modified: incubator/public/trunk/site-publish/guides/sites.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/sites.html?rev=1182994&r1=1182993&r2=1182994&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/sites.html [utf-8] (original)
+++ incubator/public/trunk/site-publish/guides/sites.html [utf-8] Thu Oct 13 17:17:19 2011
@@ -48,49 +48,49 @@
      <input name="Search" value="Go" type="submit"/>
     </form>
           <div class="menuheader"><a 
-href="/projects/index.html">Incubator Projects</a></div> 
+href="../projects/index.html">Incubator Projects</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
 href="http://www.apache.org/foundation/glossary.html#Podling">Podlings (What's that?)</a></div> 
     <menu compact="compact">
-          <li><a href="/incubation/Incubation_Policy.html">How? (Policy)</a></li> 
-          <li><a href="/incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li> 
-          <li><a href="/incubation/Process_Description.html">When? (Process)</a></li> 
+          <li><a href="../incubation/Incubation_Policy.html">How? (Policy)</a></li> 
+          <li><a href="../incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li> 
+          <li><a href="../incubation/Process_Description.html">When? (Process)</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/guides/index.html">Entry Guides</a></div> 
+href="../guides/index.html">Entry Guides</a></div> 
     <menu compact="compact">
-          <li><a href="/guides/proposal.html">Proposal Guide</a></li> 
+          <li><a href="../guides/proposal.html">Proposal Guide</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/guides/index.html">Podling Guides</a></div> 
+href="../guides/index.html">Podling Guides</a></div> 
     <menu compact="compact">
-          <li><a href="/guides/committer.html">Podling Committers</a></li> 
-          <li><a href="/guides/ppmc.html">Podling PMC (PPMC)</a></li> 
-          <li><a href="/guides/mentor.html">Podling Mentor</a></li> 
-          <li><a href="/guides/releasemanagement.html">Podling Releases</a></li> 
-          <li><a href="/guides/branding.html">Podling Branding/Publicity</a></li> 
-          <li><a href="/guides/sites.html">Podling Websites</a></li> 
-          <li><a href="/guides/graduation.html">Graduation</a></li> 
-          <li><a href="/guides/retirement.html">Retirement</a></li> 
+          <li><a href="../guides/committer.html">Podling Committers</a></li> 
+          <li><a href="../guides/ppmc.html">Podling PMC (PPMC)</a></li> 
+          <li><a href="../guides/mentor.html">Podling Mentor</a></li> 
+          <li><a href="../guides/releasemanagement.html">Podling Releases</a></li> 
+          <li><a href="../guides/branding.html">Podling Branding/Publicity</a></li> 
+          <li><a href="../guides/sites.html">Podling Websites</a></li> 
+          <li><a href="../guides/graduation.html">Graduation</a></li> 
+          <li><a href="../guides/retirement.html">Retirement</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/clutch.html">Status of the Clutch</a></div> 
+href="../clutch.html">Status of the Clutch</a></div> 
     <menu compact="compact">
-          <li><a href="/clutch.html">Current Podling Status</a></li> 
-          <li><a href="/clutch.html#steps">Assist with Steps</a></li> 
+          <li><a href="../clutch.html">Current Podling Status</a></li> 
+          <li><a href="../clutch.html#steps">Assist with Steps</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/ip-clearance/index.html">IP Clearance</a></div> 
+href="../ip-clearance/index.html">IP Clearance</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
-href="/whoweare.html">Who We Are</a></div> 
+href="../whoweare.html">Who We Are</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
-href="/sitemap.html">Site Map</a></div> 
+href="../sitemap.html">Site Map</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
@@ -104,11 +104,11 @@ href="http://www.apache.org">ASF</a></di
             </menu>
       <div class="menuheader">Other Guides</div>
     <menu compact="compact">
-          <li><a href="/guides/participation.html">Participation</a></li> 
-          <li><a href="/faq.html">General FAQ</a></li> 
-          <li><a href="/guides/pmc.html">PMC</a> (<a href="/guides/chair.html">Chair</a>)</li> 
-          <li><a href="/guides/lists.html">Mailing Lists</a></li> 
-          <li><a href="/guides/website.html">Incubator Website</a></li> 
+          <li><a href="../guides/participation.html">Participation</a></li> 
+          <li><a href="../faq.html">General FAQ</a></li> 
+          <li><a href="../guides/pmc.html">PMC</a> (<a href="../guides/chair.html">Chair</a>)</li> 
+          <li><a href="../guides/lists.html">Mailing Lists</a></li> 
+          <li><a href="../guides/website.html">Incubator Website</a></li> 
             </menu>
       <div class="menuheader"><a 
 href="http://wiki.apache.org/incubator">Incubator Wiki</a></div> 
@@ -122,9 +122,7 @@ href="http://wiki.apache.org/incubator">
    </div>
    
    <div class="span12">
-            <h2><img src="../images/redarrow.gif" />
-   Abstract
-</h2>
+            <h2><img src="../images/redarrow.gif" />Abstract</h2>
 <div class="section-content">
 <p>
 Podlings need to build a community in Apache in order to be accepted
@@ -132,9 +130,7 @@ as part of the Apache Software Foundatio
 a community is the web site.
         </p>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   Podling Website Requirements
-</h2>
+        <h2><img src="../images/redarrow.gif" />Podling Website Requirements</h2>
 <div class="section-content">
 <p>
 Podlings are, by definition, not yet fully accepted as part of the
@@ -169,13 +165,9 @@ The website lives in the following direc
            </li>
         </ul>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   Creating the Podling Website
-</h2>
+        <h2><img src="../images/redarrow.gif" />Creating the Podling Website</h2>
 <div class="section-content">
-<h3>
-   Creating A Good Podling Site
-</h3>
+<h3>Creating A Good Podling Site</h3>
 <div class="section-content">
 <p>
   Apache Project Web Sites typically include several standard pages.
@@ -225,9 +217,7 @@ The website lives in the following direc
   Dependencies: other projects that this project depends on.
                 </li></ul>
 </div>
-<h3>
-   <a name="Tool">Web Site Generation Tool</a>
-</h3>
+<h3 id='Tool'>Web Site Generation Tool</h3>
 <div class="section-content">
 <p>
   The choice of tool used to generate the web site is left to 
@@ -249,9 +239,7 @@ The website lives in the following direc
   the svn repository, e.g. parallel to the trunk of the source tree.
             </p>
 </div>
-<h3>
-   Publishing The Website
-</h3>
+<h3>Publishing The Website</h3>
 <div class="section-content">
 <p>
 The website is published by checking out the content from SVN into 
@@ -272,9 +260,7 @@ incubation status file, to describe the 
 directory which holds the published site.
            </p>
 </div>
-<h3>
-   <a name="create-website-using-wiki">Using A Wiki To Create Documentation</a>
-</h3>
+<h3 id='create-website-using-wiki'>Using A Wiki To Create Documentation</h3>
 <div class="section-content">
 <p>
         Podlings may use a wiki to create documentation (including the website) providing that follow the 
@@ -285,9 +271,7 @@ directory which holds the published site
         </p>
 </div>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   Main Incubator Website
-</h2>
+        <h2><img src="../images/redarrow.gif" />Main Incubator Website</h2>
 <div class="section-content">
 <p>Please read the <a href="website.html">Incubator Website guide</a>
       for more information about how the general Incubator site is laid out

Modified: incubator/public/trunk/site-publish/guides/website.html
URL: http://svn.apache.org/viewvc/incubator/public/trunk/site-publish/guides/website.html?rev=1182994&r1=1182993&r2=1182994&view=diff
==============================================================================
--- incubator/public/trunk/site-publish/guides/website.html [utf-8] (original)
+++ incubator/public/trunk/site-publish/guides/website.html [utf-8] Thu Oct 13 17:17:19 2011
@@ -48,49 +48,49 @@
      <input name="Search" value="Go" type="submit"/>
     </form>
           <div class="menuheader"><a 
-href="/projects/index.html">Incubator Projects</a></div> 
+href="../projects/index.html">Incubator Projects</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
 href="http://www.apache.org/foundation/glossary.html#Podling">Podlings (What's that?)</a></div> 
     <menu compact="compact">
-          <li><a href="/incubation/Incubation_Policy.html">How? (Policy)</a></li> 
-          <li><a href="/incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li> 
-          <li><a href="/incubation/Process_Description.html">When? (Process)</a></li> 
+          <li><a href="../incubation/Incubation_Policy.html">How? (Policy)</a></li> 
+          <li><a href="../incubation/Roles_and_Responsibilities.html">Who? (Roles)</a></li> 
+          <li><a href="../incubation/Process_Description.html">When? (Process)</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/guides/index.html">Entry Guides</a></div> 
+href="../guides/index.html">Entry Guides</a></div> 
     <menu compact="compact">
-          <li><a href="/guides/proposal.html">Proposal Guide</a></li> 
+          <li><a href="../guides/proposal.html">Proposal Guide</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/guides/index.html">Podling Guides</a></div> 
+href="../guides/index.html">Podling Guides</a></div> 
     <menu compact="compact">
-          <li><a href="/guides/committer.html">Podling Committers</a></li> 
-          <li><a href="/guides/ppmc.html">Podling PMC (PPMC)</a></li> 
-          <li><a href="/guides/mentor.html">Podling Mentor</a></li> 
-          <li><a href="/guides/releasemanagement.html">Podling Releases</a></li> 
-          <li><a href="/guides/branding.html">Podling Branding/Publicity</a></li> 
-          <li><a href="/guides/sites.html">Podling Websites</a></li> 
-          <li><a href="/guides/graduation.html">Graduation</a></li> 
-          <li><a href="/guides/retirement.html">Retirement</a></li> 
+          <li><a href="../guides/committer.html">Podling Committers</a></li> 
+          <li><a href="../guides/ppmc.html">Podling PMC (PPMC)</a></li> 
+          <li><a href="../guides/mentor.html">Podling Mentor</a></li> 
+          <li><a href="../guides/releasemanagement.html">Podling Releases</a></li> 
+          <li><a href="../guides/branding.html">Podling Branding/Publicity</a></li> 
+          <li><a href="../guides/sites.html">Podling Websites</a></li> 
+          <li><a href="../guides/graduation.html">Graduation</a></li> 
+          <li><a href="../guides/retirement.html">Retirement</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/clutch.html">Status of the Clutch</a></div> 
+href="../clutch.html">Status of the Clutch</a></div> 
     <menu compact="compact">
-          <li><a href="/clutch.html">Current Podling Status</a></li> 
-          <li><a href="/clutch.html#steps">Assist with Steps</a></li> 
+          <li><a href="../clutch.html">Current Podling Status</a></li> 
+          <li><a href="../clutch.html#steps">Assist with Steps</a></li> 
             </menu>
       <div class="menuheader"><a 
-href="/ip-clearance/index.html">IP Clearance</a></div> 
+href="../ip-clearance/index.html">IP Clearance</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
-href="/whoweare.html">Who We Are</a></div> 
+href="../whoweare.html">Who We Are</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
-href="/sitemap.html">Site Map</a></div> 
+href="../sitemap.html">Site Map</a></div> 
     <menu compact="compact">
             </menu>
       <div class="menuheader"><a 
@@ -104,11 +104,11 @@ href="http://www.apache.org">ASF</a></di
             </menu>
       <div class="menuheader">Other Guides</div>
     <menu compact="compact">
-          <li><a href="/guides/participation.html">Participation</a></li> 
-          <li><a href="/faq.html">General FAQ</a></li> 
-          <li><a href="/guides/pmc.html">PMC</a> (<a href="/guides/chair.html">Chair</a>)</li> 
-          <li><a href="/guides/lists.html">Mailing Lists</a></li> 
-          <li><a href="/guides/website.html">Incubator Website</a></li> 
+          <li><a href="../guides/participation.html">Participation</a></li> 
+          <li><a href="../faq.html">General FAQ</a></li> 
+          <li><a href="../guides/pmc.html">PMC</a> (<a href="../guides/chair.html">Chair</a>)</li> 
+          <li><a href="../guides/lists.html">Mailing Lists</a></li> 
+          <li><a href="../guides/website.html">Incubator Website</a></li> 
             </menu>
       <div class="menuheader"><a 
 href="http://wiki.apache.org/incubator">Incubator Wiki</a></div> 
@@ -122,9 +122,7 @@ href="http://wiki.apache.org/incubator">
    </div>
    
    <div class="span12">
-            <h2><img src="../images/redarrow.gif" />
-   <a name="Overview+of+the+Incubator+site">Overview of the Incubator site</a>
-</h2>
+            <h2 id='Overview+of+the+Incubator+site'><img src="../images/redarrow.gif" />Overview of the Incubator site</h2>
 <div class="section-content">
 <p>The source to the Incubator website lives at:</p>
 <div class="note">
@@ -144,9 +142,7 @@ href="http://wiki.apache.org/incubator">
          at "site-publish". That directory is then checked-out on the server
          to re-create the website.</p>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="Edit+the+content">Edit the content</a>
-</h2>
+        <h2 id='Edit+the+content'><img src="../images/redarrow.gif" />Edit the content</h2>
 <div class="section-content">
 <p>People with commit access to the "incubator" SVN can edit the source
          documents in the "site-author" directory. That is any ASF Member and
@@ -157,9 +153,7 @@ href="http://wiki.apache.org/incubator">
          Note that the "policy" documents need special treatment.
       </p>
 <p>Anyone else can send patches to those documents to the INCUBATOR issue tracker.</p>
-<h3>
-   <a name="Checkout+the+Incubator+SVN">Checkout the Incubator SVN site</a>
-</h3>
+<h3 id='Checkout+the+Incubator+SVN'>Checkout the Incubator SVN site</h3>
 <div class="section-content">
 <code>
 svn co http://svn.apache.org/repos/asf/incubator/public/trunk incubator<br />
@@ -170,16 +164,12 @@ cd incubator
               please ensure you use https instead of http.</note>
 </div>
 </div>
-<h3>
-   <a name="Edit+the+source+documents">Edit the source documents</a>
-</h3>
+<h3 id='Edit+the+source+documents'>Edit the source documents</h3>
 <div class="section-content">
 <p>The source content is in Anakia xdoc format at "site-author"
            directory.</p>
 </div>
-<h3>
-   <a name="Add+a+new+document">Add a new document</a>
-</h3>
+<h3 id='Add+a+new+document'>Add a new document</h3>
 <div class="section-content">
 <p>Add new documents in the site-author directories, then do 'svn add'.
   If your new documents need to be navigable from the left-hand side menu, then
@@ -188,15 +178,11 @@ cd incubator
 <p>If you are adding a new podling, then see the steps in the following section.
         </p>
 </div>
-<h3>
-   <a name="Edit+your+project+status+page">Edit your project status page</a>
-</h3>
+<h3 id='Edit+your+project+status+page'>Edit your project status page</h3>
 <div class="section-content">
 <p>The sources for the status pages are in
            <code>site-author/projects/*.xml</code></p>
-<h4>
-   <a name="create-status-page">Create Status Page</a>
-</h4>
+<h4 id='create-status-page'>Create Status Page</h4>
 <div class="section-content">
 <ol>
            <li>
@@ -251,9 +237,7 @@ cd incubator
 </div>
 </div>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="Generating+the+top-level+website">Generating the top-level website</a>
-</h2>
+        <h2 id='Generating+the+top-level+website'><img src="../images/redarrow.gif" />Generating the top-level website</h2>
 <div class="section-content">
 <div class="note">
 <note>Please generate the website yourself and check in the changes.
@@ -273,9 +257,7 @@ cd /www/incubator.apache.org<br />
 svn update
 </code>
 </div>
-        <h2><img src="../images/redarrow.gif" />
-   <a name="other">Other notes</a>
-</h2>
+        <h2 id='other'><img src="../images/redarrow.gif" />Other notes</h2>
 <div class="section-content">
 <p>Make sure that your subversion client is properly
         <a href="http://www.apache.org/dev/version-control.html#https-svn">configured</a>.</p>



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message