SVN: Documentation also by industry?

Question

I am fulfilling the dev = trunk release = branch convention. this works fine for source code, but what ppl does for documentation (unfortunately, this is in MS Word (LaTex is too much for our corporate business analysts).

Do you also save documents on a branch and merge (is it a pain ) after release?
Or do you keep documents only on the trunk?

Answer 1

Rule No. 1 of the documentation should be kept in sync with the code. Compliance with this rule requires documentation to be forked and integrated with code. When merges are required, you can use the comparison feature in Word or some other solution to let you know what has changed.

Answer 2

You must have a document with the appropriate branch. Otherwise, you may fall into a pickle with documentation that does not correspond to functions, etc. A specific branch. Especially if you need to have a separate branch for a customized version of your product that does not merge back into the trunk.