Team, CAS documentation is now part of the same branch that hosts all the code. The documentation is automatically pushed over to the docs site whenever on commits on the branch. This also includes the CAS protocol [1]. Since we are hosting all doc artifacts on the Github Pages site, and Apereo points to the same place, I am wondering if now is the time to drop the cas-protocol module and simply make all relevant changes to the cas-serve-documentation module. This has the advantage that the format is all the same, changes are automatically built and pushed over and can be frozen in time on every new release.
Makes sense? [1] https://github.com/Jasig/cas/blob/master/cas-server-documentation/protocol/CAS-Protocol-Specification.md <https://github.com/Jasig/cas/blob/master/cas-server-documentation/protocol/CAS-Protocol-Specification.md> -- 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
