Author: buildbot
Date: Wed Mar 26 14:43:48 2014
New Revision: 903764
Log:
Staging update by buildbot for thrift
Modified:
websites/staging/thrift/trunk/content/ (props changed)
websites/staging/thrift/trunk/content/docs/committers/HowToThriftWebsite.html
Propchange: websites/staging/thrift/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 26 14:43:48 2014
@@ -1 +1 @@
-1581848
+1581870
Modified:
websites/staging/thrift/trunk/content/docs/committers/HowToThriftWebsite.html
==============================================================================
---
websites/staging/thrift/trunk/content/docs/committers/HowToThriftWebsite.html
(original)
+++
websites/staging/thrift/trunk/content/docs/committers/HowToThriftWebsite.html
Wed Mar 26 14:43:48 2014
@@ -79,7 +79,7 @@
<p>Casual changes to the site are best handled through the <a
href="https://cms.apache.org/thrift/#bookmark";>javascript bookmarklet</a>. The
workflow is to browse the live site looking for pages in need of repair, then
by clicking on the bookmarklet you will be redirected to an editor for the page
in question that can ultimately commit your changes back to the site and walk
you through the publication process through the webgui.</p>
-<p>More complex changes can be accomplished by checking out the <a
href="https://svn.apache.org/repos/asf/thrift/cms-site";>svn tree</a> directly.
Commits to that tree will trigger builds of the staging site just as if you had
committed them by using the CMS webgui.</p>
+<p>More complex changes can be accomplished by checking out the <a
href="https://svn.apache.org/repos/asf/thrift/cms-site";>svn tree</a> directly.
Commits to that tree will trigger builds of the staging site just as if you had
committed them by using the CMS webgui. If you are still pining for a
nanoc-like feature to preview your changes before committing them by having a
daemon 'watch' your filesystem for edits, you really need to wrap your brain
around the CMS's <strong> commit early and commit often </strong> mantra. In
fact source control systems are far more effective at communicating changesets
than operating systems are (most of the time), and the CMS's build system is
changeset-aware based on the data it receives from svn. So think of committing
to the CMS's svn tree for thrift as just a formal way of notifying the CMS of
your changes so it can automatically (and efficiently) build them to the
staging site, just as if you were working locally with a daemon that watches yo
ur filesystem for modifications and builds them.</p>
<h3 id="updating-release-versions">Updating Release Versions</h3>
<p>The current release versioning is kept in the YAML <strong>DATA</strong>
section of the global "configuration file" <a
href="https://svn.apache.org/repos/asf/thrift/cms-site/trunk/lib/path.pm";>lib/path.pm</a>.
Update the following values and then following <b>Updating the Website</b>
section below </p>
<div class="codehilite"><pre><span class="n">current_release</span><span
class="p">:</span> "0<span class="p">.</span>9<span
class="p">.</span>1"
