I would like to suggest that docs and non-code type stuff be kept in a
different repos. The reasoning is because you have 2 completely
different types of users accessing those different files.
A code developer will probably understand that if they touch something
they shouldn't, they will need to fix it. Someone doing documentation
may not understand this, and could accidentally screw up your code if
it's intertwined with the doc files. Not that they're less smart, they
just don't tend to think about things like that.
Brian Beaudet wrote:
>OK! This is starting to come together in my poor, overworked mind. I'm
>leaning towards one single repository with many projects inside it.
>Each project contains the typical trunk, branches. So for Project1
>under trunk, I'd have all of my typical directories (build, doc,
>install, etc.).
>
>If I decide to branch from there (say for a new version of the same
>Project with specific changes) I'd copy everything from the trunk to a
>branch directory and name that branch something useful.
>
>If I have completed, releasable (or testable) version I'd copy that to
>the tags directory with a useful name that I could track myself. So,
>under tags\ I might have Release 1.0.1 and Release 1.0.2, etc or Testing
>1.0.1, Testing 1.0.5001, etc. I name these myself and I'd know what's
>next because I'm naming these manually.
>
>Am I close?
>
>
--
Brian Mathis
http://directedge.com/b/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 25 18:46:16 2004