|
Well, there is that angle as well. One can hardly carry around their favorite SCC tool and force an employer to either adopt it or interface to it at the client level.
However, I do believe this is an interesting discussion in it's own right and regardless of whatever tool an employer forces one to use...
For example, don't even get me started on IBM and the Notes email client fiasco, what a POS that thing was (and for all I know, still is.)
But point is (and at least as of when I was at IBM) that's what one was given and it's what one used...
What used to crack me up about Notes is that it used to hang (crash, otherwise become unresponsive, etc) all too frequently.
And when it did, there were on the order of up to two dozen little file turds it left in the file system and it COULD NOT be restarted (at least in any usable state) until all those little file turds were either patched up or deleted.
It got to the point where, in order to support internal users and allow them to get work done, they internally distributed a little tool whose only function was to delete or otherwise deal with all those little file turds so that once Notes hung and one rebooted (if needed, which was also all too frequent) one could run the file turd tool and at least start and use their email client again!!!!
|
|
|
|
|
 And we moan about Microsoft!
Kevin
|
|
|
|
|
Hi,
we use AccuRev in our company and it's great (http://www.accurev.com[^]).
It has some goodies:
- Good concept: so called 'streams' define, which files and which versions of them should be in use. If you put a workspace at a particular stream, you get exactly these files/versions.
- Streams can be ordered in a hierarchical way and streams inherit files/versions from their parent stream. This makes 'staging' easy (alpha - beta - release candidate, etc.).
- Issue tracking is built-in: Group all changes of files you have made for a specific task into an 'issue'. The issue can then be handled as one configuration item, e.g. to be put into another stream. The abstraction to handle whole issues instead of single files is very effective. (though it's still transparent down to the files).
- No more tag or labels needed - make a snapshot in seconds. Need bugfixes of a snapshot version? Simply put a stream at the snapshot and continue working there.
- Linux symbolic links and Windows' junctions can be handled.
- GUI and CLI, equal for Windows and Linux.
- The repository backups are easy and can be done while the server is running.
- ..and many more.. 
best regards,
pink ink
|
|
|
|
|
Now that I have my two Alpha systems running (OpenVMS 8.3) I can begin using CMS again. 
|
|
|
|
|
Does this poll only include source control systems used in commercial crap?
Seriously, where is git, mercurial, bzr, CVS (hope nobody still uses *this*)...?
|
|
|
|
|
Member 4134890 wrote: commercial crap
Steady on mate.
Member 4134890 wrote: Seriously, where is git, mercurial, bzr, CVS (hope nobody still uses *this*)...?
There is an "other" input box. Use it.
|
|
|
|
|
Ouch... Well, maybe you should add the "other" category to the results. It could, quite possibly, make the answers add up to 100%...
|
|
|
|
|
I used a licensed fork of Perforce at a very large SW company for several years and loved it.
It was lightweight and had a simple command line interface (there are of course gui tools as well), yet was amazingly flexible and powerful.
It simply and without a lot of overhead did what one typically wants from an SCC tool, yet did not present, impose, nor attempt to enforce some pre-conceived notion of development/build/test processes the way a lot of tools do.
One could create enlistments with notepad (edit or create two little files with trivial content and you're done), etc.
Unfortunately, Perforce's cost and licensing model is not terribly affordable or friendly to smaller SW development establishments/houses/companies, or I'd have bought it myself for my employer.
Given that VSS is bundled free and etc, that seems to be what a lot of programs and companies and projects end up with. And for good reason (cost-wise), given what I've seen of the price and licensing models of a lot of the commercial alternatives...
|
|
|
|
|
I use MKS Source Integrity
|
|
|
|
|
At work I do too. Can't say I'm very impressed. The features are (mostly) there, but hard to find...
At home I use zip with dates on the file. 8-)
|
|
|
|
|
Hardened SVN server setup in progress, expect to switch at next project branch.
 SS has been too buggy for too long, especially when the SS guys at MS didn't really maintain it properly between the VS98 release and the "new" SS that came with VS2005. Especially a major regression in SS 6.0d (unrepairable SS generated minor inconsistency suddenly interfered with every
get or checkout from anywhere unrelated in the repository).
 Such non-support for a critical data storage tool made me not want to bet the farm on any new MS
source control tool. Imagine how data centers would respond to similar showstoppers in the equally business critical SQL Server or in the NTFS file system.
This message is hasty and is not to be taken as serious, professional or legally binding.
I work with low level C/C++ in user and kernel mode, but also dabble in other areas.
|
|
|
|
|
I'm using VSS at the office (we use the VSS Internet plugin and we are about to migrate to TF) and SVN (Assembla's one) for my personal projects...
I prefer SVN... by far!!
I'm on a Fuzzy State: Between 0 an 1
|
|
|
|
|
Unfortunately it seems like almost all my employers so far have opted use SourceSafe, probably because its in the Visual Studio box (I can't think of any other reason they may have gone that way). 
|
|
|
|
|
I use Team Foundation now, and use SVN at home. But Vault was probably the best I've used. The install was easy, and having your code in sql server meant a backup was a simple db backup that was taken care of with all the rest
|
|
|
|
|
Same situation, work uses TF and for my own project at home I've been using SVN, which I am staring to enjoy now that I'm getting used to how it works. But the first SCC I used after ditching SourceSafe was Vault. It's an excellent, cheap system and it's free for a single developer.
|
|
|
|
|
I helped put VSS in place at work. About a year later (year ago) we switched over to subversion Just need to teach the newer folk that conflicts are not resolved by unanimously toasting the other devs changes
|
|
|
|
|
.... but if I had to it would be CListCtrl.
"Listen, and listen well. I really like the band N-Sync. My favorite member is Harpo. I think there's a Harpo. If not there should be. I will write their next hit, maybe 'A boom-boom chiky chiky boom-boom a boom-boom chiky chaka chaka cho cho.' By the way, you must beware of Betty's iron claw. They are sharp, and they hurt. And beware his song about big butts, he beats people up while he plays it! " - Master Tang (from Kung Pow: Enter the Fist)
|
|
|
|
|
I didn't for my first few years at my current job (been there over 11 years). However after getting a project that required me to write 250K lines of code over 4 to 5 years I quickly found it impossible to manage this much code without source control. The old .zip method every day was not working well. After trying cvs and wincvs, I wish I was using a long time before that. It was so much easier to revert back changes ... and then with the viewcvs/cvsweb it was also easy to view changes through the web. And I know I am forgetting multiple sandboxes (on the same development machine) and branching which are also very helpful...
John
|
|
|
|
|
What about CListCtrl? I might use it as my source control.
"Listen, and listen well. I really like the band N-Sync. My favorite member is Harpo. I think there's a Harpo. If not there should be. I will write their next hit, maybe 'A boom-boom chiky chiky boom-boom a boom-boom chiky chaka chaka cho cho.' By the way, you must beware of Betty's iron claw. They are sharp, and they hurt. And beware his song about big butts, he beats people up while he plays it! " - Master Tang (from Kung Pow: Enter the Fist)
|
|
|
|
|
I prefer Chris Maunder's CGridCtrl. Its much more functional and yes its in my cvs.
John
|
|
|
|
|
It's an antiquated Configuration management tool from a long time ago. It doesn't play with any development tools and is confusing to use. At least once it has corrupted my files.
Some of us have been trying to get our company into the '90s and get a better CM tool but the PHBs are used to hearing about Razor so we don't change.
|
|
|
|
|
|
I used ClearCase for years, both as a user and as an administrator. It has got to be the most convoluted, God-awful RCS on the planet.
Its biggest drawback is that everything occurs over the network. You create a virtual drive that points to the versioned object (VOB). Files that are checked out (locking system = bad) are local to your machine. Everything else is coming from the server. Builds are slow as hell.
Multi-site support requires someone to be a "merge master" and put the right bits in the right places every morning when the remote packet is merged. Been there, done that, not going near it again.
Subversion is a much better product. Smaller, easier to administer, and need only rely on HTTPS instead of custom protocols. Since every engineer is responsible for merging his own changes, no one has to be a merge master at 0700 before people hack on the code for the day.
ClearCase. *BLECH* 
Paul
|
|
|
|
|
I have to use clearcase
Besides the issues you mention "hiccups" in the integration to VS have cost me several hours and none of the interface is intuitive. Lacking in common features like "check in but keep checked out".
I've used most of the other products mentioned in other jobs, Subversion being my favorite. Any are better than ClearCase. Someone spent the $$ .. now I am stuck with it.
|
|
|
|
|
I worked at Rational for years before and just after they were bought out by IBM.
The situation is even worse than both you suggest, though you hit many of the problems.
ClearCase also maintains client enlistment state information on both the Server AND the Client.
*AND* both sets of data have to both exist and agree, or the clients' enlistment becomes unusable without admininstrator intervention.
It was not uncommon for the client-side file turds that store the Client-side Client state information to become corrupted (HDD dropout or failure, BSOD, etc), and thereafter have the client be unusable until things were patched up.
After a while I personally got in the habit of routinely using a CMD + Perl script to detect files that were changed in my enlistment(s) and squirrel them away somewhere.
That way, when ClearCase quit working on my machine because one of the file turds got wacked or wacky and if the administrators' were not available or unresponsive, I could at least recover my state by creating a new enlistment and starting over.
Well, even that was not always possible, not before the original client was recovered or deleted.
But at least I *could* recover.
However, doesn't all that sort of negate the reason for having SCC in the first place? If users have to squirrel away private copies of their code to protect it from the SCC system itself AND often work outside of or around the SCC system in order to get their work done, what's the point???
FWIW and as an employee of Rational we used to routinely file bug reports and usability dings etc against ClearCase, but all that did is incur the wrath of management who believed the boneheads who owned ClearCase when they said we were just whiners and weren't qualified to pass judgement on an enterprise-capable SCC system.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
