|
Having tried others including Bazar, which should be renamed to Bizarre, I settled on Subversion and have never regretted the decision.
I may not last forever but the mess I leave behind certainly will.
|
|
|
|
|
Subversion does do version labelling. Just create a branch at the point you want labelled.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
We have used Sourcegear Vault for several years, and its APIs let us integrate it into our custom CRM system.
|
|
|
|
|
Having used VSS (Visual Source Sausage<g>) years past, once we switched to SVN, we never looked back.
One thing we do is use multiple on some projects with longer development cycles.
We have just started using Hg locally against source in SVN, just to support mini-commits that might break a build, but need to capture current development source state.
The hardest thing in the switch is moving from Repository Centered viewing. In the beginning I was constantly using SVN Repo Browser to "see" what was inside the server.
|
|
|
|
|
Gary R. Wheeler wrote: I'll probably also take a look at Subversion, given its popularity. I doubt I would consider Git, as we don't need distributed access, the learning curve sounds steep, and there's no Visual Studio integration.
TFS or Subversion would be the best bets then. If you also want application life cycle management and VS integration then TFS or Git would be the choices as VS is becoming increasingly Git-friendly.
There are a few GUI tools for Git but no real VS integration.
I've started using Git in my current contract and I've settled on Git Extensions. It's not proper VS integration but good enough. You get a basic VS toolbar for Commit, Pull and Push. You can right-click on a tab and get file history and file diffs, etc.
Kevin
|
|
|
|
|
I've often used multiple programs, depending on the project. I could've easily checked SVN, TFS and Perforce.
At this point in the survey I'm surprised that TFS has such a lead on Git. Then again it's coming from the Microsoft-only shops. Nothing wrong with that...please don't hate. 
|
|
|
|
|
When I saw this survey I thought: why this a radio not set of checkboxes? Really not everyone can work on internal projects or dictate that kind of thing to customer.
No more Mister Nice Guy... >: |
|
|
|
|
|
.....I've got to admit, the more I use git the more I'd never consider anything else.
For a long time I used SVN and enthused about it - with a good setup it just *works* which is something we can't say about, for example, office, visual studio, windows, yadayada all the software we use day to day. But git has taken the throne for me.
The large supply of free online services like GitHub have massively boosted it's popularity, and for what it can cost in terms of a bit of a syntactic learning curve, you get it back so many times over when you start working with pull requests and having to branch regularly.
There are still moments of frustration when someone gets something wrong and you end up with huge merge commits, but as a team starts getting to grips with git, it can really be of benefit.
|
|
|
|
|
 *pukes
|
|
|
|
|
Hang on, it gets even better: The old projects in Source Safe actually are great Access applications with such an adcanced design that you probably never heard of it. 
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript.
|
|
|
|
|
yep, that's exactly what we've got Access 97 databases, tons of the little s**ts
we've got another SS db for the more 'advanced' vb6 apps.
Looks like we might be migrating to use ClearCase as we've found that some other part of the company has already got the licenses for it.
|
|
|
|
|
There really must be a joke in there, VSS, Access, VB6 and from Ireland.
While we may be a little more up to date the idea that we will use a tool is often dictated by "Oh some other department already uses it" no matter how crappy the dammed thing is.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Yes, Really!
I've mentioned it to my boss several times but when he sees the cost of upgrade it goes right back out the other ear. He is also blind to the time savings that we would gain after an upgrade.
|
|
|
|
|
I think I've actually got my boss convinced that we need to upgrade. We've got several SourceSafe "data bases", half of which are at or near the 5GB size limit. The nightly backup / ANALYZE run takes six hours just to churn through the three most active data bases.
If you were to upgrade, what would you upgrade to? Team Foundation Server? SourceGear Vault? Or would you go with one of the other source control tools that don't integrate with Visual Studio?
Software Zen: delete this;
|
|
|
|
|
I am envious. Good job in convincing him. We run /ANALYZE only on the weekend and hope for the best. We have taken a look at TFS a couple of times but there is always a reason to delay it.
|
|
|
|
|
1 or 2 occurrences of a corrupted VSS DB (which then had to be restored to a previous version including some data loss) were enough to convince the management to switch to another source control system
We switched to TFS however and works great so far (other than that it needs a hell lot of resources to run it)
|
|
|
|
|
Upgrade cost?? I accepts that there are incidental costs such as productivity dipping while the team gets to grips with a new system, but there are several very competent free-as-in-cash systems such as SVN or GIT which integrate very nicely with VS & the Windows shell. How do you arrive at a non-trivial upgrade cost?
--
What's a signature?
|
|
|
|
|
I've seen GIT mentioned in other posts as well. I will take a look at it and work how to suggest it if it is good. I've taken a look at other no-cost source control systems but my boss has it in his head that they are no good.
|
|
|
|
|
you should be allowed to vote for more than one option. I work with different systems depending on the project or work that I am doing.
you want something inspirational??
|
|
|
|
|
I agree with you... we do not rely on single source control,its purely depends on client and project.
Thanks,
•…♥…ЯΚ…♥…•
|
|
|
|
|
Smallish group. Each using different languages for different purposes. No one to really control source with.
Actually - when I start to mangle some of the my or the directors code/queries I make a parallel copy. When those work I do renaming and they slip into place without the user's knowing a thing.*
Wait a minute . . . when did the users every know anything, anyway?
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "As far as we know, our computer has never had an undetected error." - Weisert | | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
We use two products that are on the list, and I want to report that.
Additionally, Subversion is a version control system, not a source code control system.
|
|
|
|
|
Until very recently I was working at a site that still used PVCS. Still did it's job mind - albeit with some extra procedures wrapped around its use.
Then I "moved on" to this site to use SourceSafe 
|
|
|
|
|
Being a control freak, I love PVCS. You need to work on a file YOU and only YOU can modify it. If you needed a file and someone else had it you knew who to go bug/help/pester to get the file. None of this I can modify while you modify then someone has to figure out how to make it work with both our changes crap.
|
|
|
|
|
Big, old project. Too late to change now!
Ian
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
