We’re about to start a new project, and our client’s current application is .NET versioned in SourceSafe. However, we use Subversion internally. This will likely be a ‘one-time’ delivery (complete application rewrite), so they could easily do a checkout from our repo, then export, and import into their SourceSafe repo. However, my fear is that if we have some edits or do future maintenance, that it becomes much more difficult to manage. Any thoughts on how best to handle this?
EDIT:
I’m not sure if it makes a difference, but there is a low-probability that the client will make changes. If they do, it will be after we are 100% done, which makes it easier to manage. If we were both making changes simultaneously, then I would probably suggest I give them write access to our repo for their project, and we manage it that way. I’m trying to be forward thinking though, because there is a strong chance they would want us to come back and do more work with them.
Another option is to provide them with access to your svn repo (for their project only) and give them support, links, etc. Once they see the light they may not want to use anything else…
I think I would do it that way until you have to make a decision about ssafe. Maybe before you have to make a decision it will just go away.
I did have an experience with this in the past. For some reason the company we were subcontracting was using CVS internally, but SourceSafe for external client facing stuff. I took over the project and put it into svn. The contractors were happy with that.
EDIT:
Additionally, it is possible to have a master/slave svn repo set up. Not sure if that helps in this situation.
Another possibility is asking them if they would host an svn repo if you set it up and admin’ed it at first.
All in all, it is probably best to talk to the client to work this out. See what ideas you can come up with. Maintaining two ACTIVE repos is not a good idea.