So I was about to create a dump of my subversion repository so I could split multiple projects into separate repositories.  But then I got to thinking.  Why do I want to create a dump?  Well, the only good reason I could come up with was revision history.  That reason wasn't good enough.

The source that I wanted to split out was some common/shared libraries.  Collaborating with a team member, we decided there were two compelling reasons why we don't need the history up to this point in time.  First, the code base is fairly small and young, but stable.  That is, we are confident that it does what it is supposed to (we have tests).  Second, the code has never been released.  There are no production products using this code (yet).  So, the need to go back to a "release" revision simply doesn't exist.

Bottom line:  Don't go through the trouble of svnadmin dump and svndumpfilter if you don't have to.

posted on Thursday, May 8, 2008 11:01 PM
Filed Under [ Agile Builds & CI Productivity Subversion ]

Comments

No comments posted yet.

Post A Comment
Title:
Name:
Email:
Comment:
Verification: