[OPEN-ILS-DOCUMENTATION] Using master branch to test docs

[Remington Steed]

Hi DIG,

In response to Yamil's question at the meeting today, I had this idea.  When publishing docs, we could use the master branch as our test version. If it breaks, it's okay because it's only the dev version of the docs!  If people check the 2.5 version (or other versions) of the docs, they will still work fine.  Then you can fix the dev version, check it the next day, and then apply your fix to the current docs branches (e.g. 2.5 and 2.4).

So, you should still test AsciiDoc syntax on your own machine (or using Gist, as explained here<http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:how-to-contribute-documentation&#quick_start_for_new_contributors>), then push your contributions to the master docs as the next level of testing, then finally push your contributions to the other versions of the docs.

Remington

--
Remington Steed
Electronic Resources Specialist
Hekman Library, Calvin College
http://library.calvin.edu/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.georgialibraries.org/pipermail/open-ils-documentation/attachments/20131205/b1ec4da1/attachment.htm>