Author: buildbot
Date: Wed Jun 12 16:32:32 2013
New Revision: 865432

Log:
Staging update by buildbot for trafficserver

Modified:
    websites/staging/trafficserver/trunk/cgi-bin/   (props changed)
    websites/staging/trafficserver/trunk/content/   (props changed)
    websites/staging/trafficserver/trunk/content/index.html

Propchange: websites/staging/trafficserver/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jun 12 16:32:32 2013
@@ -1 +1 @@
-1492266
+1492268

Propchange: websites/staging/trafficserver/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Jun 12 16:32:32 2013
@@ -1 +1 @@
-1492266
+1492268

Modified: websites/staging/trafficserver/trunk/content/index.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/index.html (original)
+++ websites/staging/trafficserver/trunk/content/index.html Wed Jun 12 16:32:32 
2013
@@ -234,10 +234,8 @@
 
           <li>
           <a 
href="https://cwiki.apache.org/confluence/display/TS/Apache+Traffic+Server";>Wiki</a>
-          </li>
-
-          <li>
-          <a href="https://blogs.apache.org/trafficserver/";>Our blog</a>
+          and <a href="https://blogs.apache.org/trafficserver/";>Our blog</a>
+          <p>Collaboration and interesting topics around the project</p>
           </li>
 
         </ul>
@@ -255,7 +253,7 @@
     <div class="twelvecol">
       <div id="blurbbox">
         <ul>
-          <li><b>June 12, 2013:</b>You can now follow Traffic Server on twitter
+          <li><b>June 12, 2013:</b> You can now follow Traffic Server on 
twitter
           (@trafficserver) and Google Plus. Also see the link to our new blog 
above!
           <li><b>June 10, 2013:</b> Our latest developer release,
             v3.3.4-dev, is now available from the download page.</li>


Reply via email to