[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: subversion repository structure

From: Bob Archer <bob.archer_at_amsi.com>
Date: Fri, 16 Oct 2009 10:21:59 -0400

> my svn respository structure is the following
> yes. it's very common structure as you know.
> repository name : testproject
> testproject/server
> testproject/server/trunk
> testproject/server/tags
> testproject/server/branches
> testproject/client
> testproject/client/trunk
> testproject/client/tags
> testproject/client/branches
> now.. i have to add documentation folder which contains user manual or
> project related document.
> how can i compose the documentation folder in my repository ?
> * make another repository for documentation ?
> * make testproject/documentation ?
> * make server/documetation and client/documentation?
> what is the best practice?

It really depends on you. If your documentation is worked on as a single unit, I would say make testproject/doc folder. However, if your doc is totally separate for client and server then put a doc folder in trunk of each of those.

But, if testproject is all one project it might make more sense to have:


Of course YMMV and having trunk/tags/branches for each client/server and documentation may just be what you need. It really depends on the granularity of your project, the tools and versioning. A general guideline I follow is if everything is versioned and/or deployed as a unit then put it together. The way you have it would imply to me that while client and server are all part of your testproject "application" they are developed and versioned separately.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-16 16:23:04 CEST

This is an archived mail posted to the Subversion Users mailing list.