svn commit: r1581870 - /thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md

[jo...@apache.org]

Author: joes
Date: Wed Mar 26 14:43:44 2014
New Revision: 1581870

URL: http://svn.apache.org/r1581870
Log:
comments on workflow mindset regarding commits

Modified:
    thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md

Modified: thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md
URL: http://svn.apache.org/viewvc/thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md?rev=1581870&r1=1581869&r2=1581870&view=diff
==============================================================================
--- thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md (original)
+++ thrift/cms-site/trunk/content/docs/committers/HowToThriftWebsite.md Wed Mar 26 14:43:44 2014
@@ -14,7 +14,7 @@ Publishing the staging site is doable th
 
 Casual changes to the site are best handled through the [javascript bookmarklet](https://cms.apache.org/thrift/#bookmark).  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.
 
-More complex changes can be accomplished by checking out the [svn tree](https://svn.apache.org/repos/asf/thrift/cms-site) directly.  Commits to that tree will trigger builds of the staging site just as if you had committed them by using the CMS webgui.
+More complex changes can be accomplished by checking out the [svn tree](https://svn.apache.org/repos/asf/thrift/cms-site) 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 ** commit early and commit often ** 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 your filesystem for modificat
 ions and builds them.
 
 ### Updating Release Versions