I don't think it makes sense to spend time on SVN support.
Any .NET shop who is stuck on SVN is NOT going to outsource their deployment/hosting to AppHarbor. It's better to serve the people on the cutting edge first.
Wrong. The reason why Git/Mercurial users are more likely to use AppHarbor is that AppHarbor is probably more likely used by open source projects. Enterprises, where SVN is actually the preferable system, are less likely to host on AppHarbor (or EC2 or Azure).
The issue isn't cutting edge of the source code control system (which frankly makes no sense if you actually understand Git and SVN), but business model.
I don't think we're going to be supporting SVN natively anytime soon..
It's really easy to use git-svn to import your SVN repo to git, and you
can use it along with svn. You can then deploy to appharbor with git and
use SVN as usual.
If people need any help with git and git-svn though we're happy to help!
Pondering when I'm going to be able to start pushing production sites to AppHarbor. Does anyone have any experience to share in terms of robustness, scalability, support etc?
[Ed: I'm not poking fun, I actually think for a .NET platform those make sense]