Forum OpenACS Q&A: Combined CVS documentation

Collapse
Posted by Joel Aufrecht on
I've pulled together text from

https://openacs.org/4/checkout
https://openacs.org/forums/message-view?message_id=185506
https://openacs.org/contribute/cvs_guidelines
http://rubick.com:8002/openacs/contributing

revised, updated, and simplified it, and put it into the standard documentation:

https://openacs.org/doc/openacs-5-1/cvs-guidelines.html

Feedback welcome!  I would like to take down the checkout and cvs guidelines pages, and Jade's page, and point to this document instead.  What changes are needed before we can do that?

Collapse
Posted by Rocael Hernández Rizzardini on
Hey Joel, thanks, this will be really useful for any day to day openacs developer; and maybe too long for a newbie, the question is how to make it easier for them. Probably a new dev is willing to get the latest code from a given branch, might be useful to quickly introduce them how to get the latest stable, per release number or branch development code from CVS and then reference to this detailed CVS documentation.

Comments?

Collapse
Posted by Joel Aufrecht on
What about putting "Using CVS with OpenACS" first, and "OpenACS CVS Concepts" second?
Collapse
Posted by Torben Brosten on

Joel, my newbie experience says that a long document is not a problem if it is well organized with a TOC at top and there are FAQ-like links that jump to sections on the page.

Will this page https://openacs.org/doc/current/releasing-package.html be included?

Also, I find these links useful cvs references.

cvs manual

  • Piskorski's cvs refs
  • backup with cvs
  • merging 2 file heirarchies with cvs
  • Torben

    Collapse
    Posted by Joel Aufrecht on
    I reformatted it and added the suggested links.