I'm investigating to install subversion at work, for our projects. If anyone has already tried it, esp. on perl / mod_perl projects, esp. with mod_dav_svn (subversion over mod_dav), I'd be happy to know what you've done with it and how well it worked. (Side note -- I remember Hugo having said once that it was possible to consider replacing Perforce by subversion to keep the bleadperl sources).
I've been following subversion for a long while. I still receive the announcements. They are getting very close, but have not yet released a 1.0 version. I think until subversion's own developers feel confident enough to call it 1.0, it will not be safe to use in production work.
I intend to start using it as soon as possible after 1.0 comes out, though.
Re:Wait for 1.0
darobin on 2002-08-31T16:59:12
At OSCon, Greg Stein said they were calling it alpha because it is VC software, otherwise it'd be a "late beta". That's not to say go ahead and use it on something critical, but apparently he was rather confident that it could be used in production, perhaps with overly eager back ups at first. SV has been self-hosting for over a year now, which is already very good.
I'd love to hear about SV experiences too. I'll sure start using it soon.
Re:So far, so good
chromatic on 2002-08-31T18:47:06
Are you using the Sleepycat backend? It's been a while since I looked into it, but I seem to recall that's how they implement the non DAV bits.
I'd really like to be able to use svn for my own, mostly single-user purposes. Any pointers?
Re:So far, so good
autarch on 2002-09-01T01:21:50
I think it's berkeleydb that it uses, but the URLs are just file:///path/to/repository
I've had no trouble with it to speak of. It's enough like cvs to be really easy to switch to, but it's just better. If you've used CVS, you'll have no trouble with it.
