Any plans to support Subversion?

Thank you very much for this information and for your opinions and thoughts
on SVN.

We have not yet used SVN enough to understand the losses or benefits of
copying for tagging and branching, but I agree, it is a little strange
after using CVS.

To me, the best benefit of SVN is the atomic commits primarily from the
perspective that revision numbers are per-commit, not per-file and log
messages are attached to the revision. This allows us to do for example a
change request or a bugfix and have the source control system record
automatically what constituted that change request or bugfix rather than
having to record this manually in documentation or cross references.

I agree that the proprietary database format is a step backwards and makes
me nervous should something happen to the repository.

Ultimately, I'd love to see a standard relational database like SQLServer
or MySQL used as the backend to the source control system. That way you can
be confident of the integrity of the contents, perform safe backups,
utilise exising knowledge and infrastructure and have the ability to layer
additional functionality on the system (like reporting).

Thanks again and I wait eagerly for your "Pushok SVN proxy" release!

Following is an email that I sent you however I thought it would be good to
post it here as well.

Firstly, I’d like to say how impressed I am with your software. I think
your plug-in is probably the only comprehensive CVS SCC interface worth
considering for Visual Studio .NET.
One of the issues that we face however, which is inherent in CVS, is that
you cannot cleanly rename files nor move files between directories and
maintain version history.

We have been monitoring an open-source revision management product called
subversion (subversion.tigris.org) which you may already be aware of which
provides a superior alternative to CVS. For example, subversion addresses
the renaming and file moving issues that CVS has as well as providing many
other significant improvements over CVS.

The designers of Subversion used CVS as a model and as a result, its
command line is very similar to that of CVS.

Subversion has only just recently been promoted to a version 1.0 status and
is beginning to be widely used amongst the community.

Unfortunately, while there are a few independent projects working on a
Visual Studio .NET SCC based plugin for Subversion, none of them are
anywhere near the quality or comprehensiveness of your product.

Do you have any plans (please!) to create a version of your software to
support subversion?

On the surface, it would appear to me that this should not be a difficult
task for you to do. You have already done the most difficult part –
implementing the SCC interface. Since Subversion has a similar command line
interface, it would seem to be a simple task to modify your software to
interface to the subversion command line program.

Your thoughts would be appreciated.