svn commit: r983609 - in /websites/staging/directory/trunk/content: ./ fortress/developer-guide.html

[bu...@apache.org]

Author: buildbot
Date: Thu Mar 24 17:44:14 2016
New Revision: 983609

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/fortress/developer-guide.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Mar 24 17:44:14 2016
@@ -1 +1 @@
-1736473
+1736475

Modified: websites/staging/directory/trunk/content/fortress/developer-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/fortress/developer-guide.html (original)
+++ websites/staging/directory/trunk/content/fortress/developer-guide.html Thu Mar 24 17:44:14 2016
@@ -768,11 +768,13 @@ $ <span class="n">vi</span> <span class=
 <p>We have to wait at least 24 hours for all mirrors to retrieve the uploaded files before making any announcement.  I'd recommend you to wait for 48 hours because some mirrors might lag due to various issues.</p>
 <h3 id="step-14-update-the-links-in-web-site">Step 14: Update the Links in Web Site<a class="headerlink" href="#step-14-update-the-links-in-web-site" title="Permanent link">&para;</a></h3>
 <p>Update the links to new distributions in [Downloads] page.</p>
-<p>There are a few places to modify :
-<em> /lib/path.pm : update the $version_fortress variable with the new version.
-</em> /content/index.mdtext : same here, update the <!-- FORTRESS project --> section, which contains the version.
-<em> /content/fortress/news.mdtext : add the news on top of thise page
-</em> /content/fortress/download-old-versions.mdtext : add a new line on top of the array, which refers to the latest version before the new one</p>
+<p>There are a few places to modify :</p>
+<ul>
+<li>/lib/path.pm : update the $version_fortress variable with the new version.</li>
+<li>/content/index.mdtext : same here, update the <!-- FORTRESS project --> section, which contains the version.</li>
+<li>/content/fortress/news.mdtext : add the news on top of thise page</li>
+<li>/content/fortress/download-old-versions.mdtext : add a new line on top of the array, which refers to the latest version before the new one</li>
+</ul>
 <p>Commit the changes, and publish the web site, you are done !</p>
 <h3 id="step-15-wait-another-24-hours">Step 15: Wait another 24 hours<a class="headerlink" href="#step-15-wait-another-24-hours" title="Permanent link">&para;</a></h3>
 <p>We need to wait until any changes made in the web site and metadata file(s) go live.</p>