All systems go. We are in business, and changes to the documentation module are automatically pushed over to the docs site. (If you have a watch on the repo, sorry about the noise)
From: Marvin Addison [mailto:marvin.addi...@gmail.com] Sent: Thursday, December 11, 2014 1:28 PM To: cas-dev@lists.jasig.org Subject: Re: [cas-dev] Making docs available in git repo? In the past, we have been making out-of-band mods to the CAS documentation. This is painful and unnecessary [1]. I'll take your word for it, though I am a bit surprised. This allows pull requests to contain mods to the docs in one changeset rather than going back and forth between branches. I can see the value in that, but I don't think every code change will include documentation simply because it's more convenient. But I'm hopeful that making it easier will encourage better habits over time, so I'm on board with your proposal. there is no extra work required of the contributor, other than making sure the docs are updated as well :) No small task ;) M -- You are currently subscribed to cas-dev@lists.jasig.org <mailto:cas-dev@lists.jasig.org> as: mmoay...@unicon.net <mailto:mmoay...@unicon.net> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
