Versions is very cool... but doesn't it seem like they've missed the boat a little?
Git has effectively taken the world by storm recently, with a slew of web-based interfaces to people's push points and a huge amount of developer mindshare.
I think you underestimate the number of users SVN has now and will continue to have. As SVN goes more and more mainstream companies will stick with it once they have it up and running. Switching to the latest and greatest VCS all the time is not a good use of time and resources.
Yep. I work at a rather large avionics company, which still mostly uses ClearCase. It's often an uphill battle to get projects moved into Subversion. Git?... not for a long time here, methinks.
If you're at a "large avionics company" using ClearCase, you're probably not using Macs with "10.4.9 and higher". (Because IBM says "At this time there is no plan to support ClearCase on Macintosh OS X, and it has not been tested for use on X11".)
It may be a good rule to support the median VCS if you're going after the median consumer, but a program for developers on recent versions of Mac OS X is not aiming at median consumers.
Touché, few Macs here, though I was just meaning to offer a datapoint for not-everyone-moving-to-Git-yet... Slightly useless in this context, I guess. :-)
I think I used to work there, and all I can say is, "I'm sorry."
I managed to get Ruby used there on our contracts. Maybe you could get Git into the workflow? The easy sell is that Git is a better backup scheme than any other backup scheme ever devised, because of the distributed nature of projects.
I suspect that most OSS projects will begin to migrate soon if they haven't already.
Git makes migration from SVN so easy there is very little reason not to do it, and with free web-based collaboration points. Given git-svn, you can still have SVN be a central storage point and still use git locally, so there is basically no downside to using it. It's hard to imagine how it wouldn't take over the OSS software world.
SVN is what many 'ugly majority' corporations are starting to move to. Now that is stable and big enough and has enough mindshare to become "the default".
> SVN is what many 'ugly majority' corporations are starting to move to.
Not a big deal. Of course mediocre developers are going to choose mediocre tools. That doesn't mean good developers should blindly follow their lead, though.
Someone pointed out to me that Versions will work with sites using self-signed certificates if svn has been previously allowed to connect to the site (from the command line).
pardon my ignorance - but how can i setup versions with my SVN repo and my local checkout? I was able to give it the login to my svn repo and that worked fine, but no clue how to get it to recognize my local svn checkout
Without knowing anything about Versions, why not just `svn ci` whatever you have modified locally, then re-checkout the repo again using the client? Totally understood if it's a big download, just throwing it out there as an option.
Git has effectively taken the world by storm recently, with a slew of web-based interfaces to people's push points and a huge amount of developer mindshare.
This might have been big money a few years ago.