I have a svn (1.5.x) repository on my server and use bzr-svn to access it. I and another developer push our changes to the server at logical points. On the server we have a simple svn workspace which we update when we want to publish our changes.
Works quite nicely. Also, you have the flexibility of using the regular svn client.
I haven't tried working with the 100% distributed solution as the current solution works. As there are only two developers we don't really have much need for branching.
If you want to use a DVCS you could also consider bzr (apart from git and hg).
Comments
I have a svn (1.5.x) repository on my server and use bzr-svn to access it. I and another developer push our changes to the server at logical points. On the server we have a simple svn workspace which we update when we want to publish our changes.
Works quite nicely. Also, you have the flexibility of using the regular svn client.
I haven't tried working with the 100% distributed solution as the current solution works. As there are only two developers we don't really have much need for branching.
If you want to use a DVCS you could also consider bzr (apart from git and hg).