Author: buildbot
Date: Mon Jan  4 23:15:01 2016
New Revision: 977066

Log:
Staging update by buildbot for slider

Modified:
    websites/staging/slider/trunk/content/   (props changed)
    websites/staging/slider/trunk/content/developing/releasing.html

Propchange: websites/staging/slider/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Mon Jan  4 23:15:01 2016
@@ -1 +1 @@
-1722982
+1722983

Modified: websites/staging/slider/trunk/content/developing/releasing.html
==============================================================================
--- websites/staging/slider/trunk/content/developing/releasing.html (original)
+++ websites/staging/slider/trunk/content/developing/releasing.html Mon Jan  4 
23:15:01 2016
@@ -628,7 +628,8 @@ updated by now to reflect the released v
 <em>The remaining changes should really be modifying the references to the 
latest release to the new version.</em></p>
 <p>The download details for the latest release needs to be updated after 
mirrors are updated in . </p>
 <p>In particular, review <code>content/downloads/index.md</code></p>
-<p>After any changes, <a href="https://cms.apache.org/slider/publish";>trigger 
a site rebuild</a>.</p>
+<p>After any changes have been committed to SVN, wait 60-90s, then
+<a href="https://cms.apache.org/slider/publish";>trigger a site rebuild</a>.</p>
 <h3 id="finish-the-jira">Finish the JIRA<a class="headerlink" 
href="#finish-the-jira" title="Permanent link">&para;</a></h3>
 <p>Log the time, close the issue. </p>
 <h3 id="example-releaseproperties-file">Example release.properties file<a 
class="headerlink" href="#example-releaseproperties-file" title="Permanent 
link">&para;</a></h3>


Reply via email to