Comments on: Subversion Turns 1.5

By: James Kovacs

James Kovacs — Wed, 13 Aug 2008 20:19:23 +0000

@Denver – Come to think of it, one of the developers of VisualSVN Server informed me that they support Windows auth out-of-the-box. I haven’t investigated, but I’m going to be using it for a client project coming up. Plus VisualSVN Server is free. (VisualSVN itself costs money, but is honestly worth every penny I paid for it.)

@Mike – Maybe developers have bad taste. Personally I like the new icon set.

By: MIke

MIke — Wed, 13 Aug 2008 20:13:53 +0000

Why is it that the graphics of open source projects suck so bad? The new overlay icons ore horrible. Sheesh.

By: James Kovacs

James Kovacs — Tue, 05 Aug 2008 15:48:02 +0000

@Denver – No, I haven’t investigated more.

By: Denver

Denver — Sun, 03 Aug 2008 06:10:49 +0000

Have you found out more on the topic of setting up Kerberos/NTLM?

By: James Kovacs

James Kovacs — Thu, 10 Jul 2008 19:05:06 +0000

@Robz – Contrary to popular belief, I don’t subscribe to everyone’s blog. I’ve added yours to my reader. You’ve got a month to keep me interested… :^P

By: Robz

Robz — Thu, 10 Jul 2008 00:44:11 +0000

I am guessing I am not in your blogroll…

http://ferventcoder.com/archive/2008/06/23/subversion-1.5.0-released.aspx

By: James Kovacs

James Kovacs — Tue, 08 Jul 2008 15:37:11 +0000

@Ivan – That’s excellent that Windows auth just works! Yet another reason to give VisualSVN Server a try. I’ve used it before and like the fact that it’s a drop-in solution. Although Ivan didn’t mention it because he’s probably too modest, VisualSVN is an absolute must-have if you’re using Subversion and Visual Studio. I can’t recommend it enough.

@Mark – I did like the fact that the CollabNet Subversion package set up svnserve and/or Apache for me as it used to be a lot more complicated. I was ready to write a glowing review of the package when I noticed that quite a few of my repositories were no longer accessible with "svnadmin: Failed to load module for FS type ‘bdb’". I expected CollabNet’s package to be a drop-in replacement and it wasn’t. I can fully understand your position in wanting to provide an excellent, headache-free experience for your customers, though I respectfully disagree with CollabNet’s strategy. Yes, BerkeleyDB is more complicated. I’ve had problems with it in the past, though I solved them. FSFS just works. So I completely agree with the decision to make FSFS the default for new repositories. My problem with the CollabNet Subversion binaries is that you will have many customers with some older BerkeleyDB-based repositories. (e.g. Me! Though this will be true of any long-term user of Subversion as BDB was the default for a long time.) The package breaks backward compatibility badly without so much as a warning on the download page. IMHO you either need to provide a clear warning on the download page that BDB isn’t supported or add it back in for backward compatibility.

By: Mark Phippard

Mark Phippard — Sat, 05 Jul 2008 18:58:22 +0000

The CollabNet binaries are aimed at our CollabNet Subversion customer and include the components that we feel provide the most reliable version of Subversion and the version we can maintain our SLA’s with. BerkeleyDB is very reliable, IF you know what you are doing. You do not have to troll the Subversion users@ mailing list and other forums for long to see all of the problems people have with BDB repositories. So we made the decision not to include it in our binaries.

You also do not mention in your blurb that the CollabNet Subversion package will automatically setup svnserve or Apache to run as a service, and also includes ViewVC which it will also automatically configure for you.

By: Ivan Zhakov

Ivan Zhakov — Sat, 05 Jul 2008 07:02:01 +0000

Please note that VisualSVN Server supports Windows authentication and authorization (!).