Alex Rivera | Logout

How would you organize a Subversion repository for in house software projects?

Asked 2008-09-09T04:19:24.997
19

I work for a company whose primary business is not software related. Most documentation for using source control is written with a development team writing for commercial or open source projects in mind. As someone who writes in house software I can say that work is done differently then it would be in a commercial or open source setting. In addition there are stored procedures and database scripts that need to be kept in sync with the code.

In particular I am looking to get suggestions on how best to structure the repository with in house software in mind. Most documentation suggests trunk, branches, tags etc. And procedures for keeping production, test and development environments in sync with their respective sections in the repository etc.

svn version-control
Edit
Report

3 Answers

3

You could use a service like www.unfuddle.com to set up a free SVN or GIT repository.

We use Unfuddle and it's really great. There are free and paid versions (depending on your needs).

Or, you could of course set up a local copy. There are plenty of tutorials to be found via Google for that: http://www.google.com/search?rlz=1C1GGLS_enUS291&aq=f&sourceid=chrome&ie=UTF-8&q=set+up+svn

answered 2008-09-09T04:24:03.237
2

I agree with using the common conventions of trunk/branches/tags. Beyond that, I think you might be looking for something like my answer at How do you organize your version control repository?.

answered 2008-11-20T01:09:34.097
0

I believe in following the basic pattern with a project dir with trunk,tags,branches beneath it. I usually like to setup the top level like this

Projects holds all of the individual project or modules Releases holds release tags that involve multiple modules Users holds private user branches Admin holds my hook scripts, backup scripts etc.

The release tags are useful if you have a product that is made up of several modules that all may be a different tags for a specific release (one ring to bind them and all that). It makes it easy for source escrow and for developments to reference what made up release 1 or 2.

answered 2008-09-18T20:46:16.203

Your Answer