|
Here is how our team uses it
Snapshot views only - no dynamic views
UCM enabled
activity/package/changeset tracking
component/project and component-dependency(composites) utilized
yearly trunk integration stream
monthly iteration development stream
team shares streams, snapshot views provide isolation (reduces branching+merging, forces early integration)
Some Pros
low maintenance - only 2-3 days of admin time per year thanks to UCM
unix heritage means that command line tools are as complete as GUI tools
command line tools generate output designed to be parsed
awesome merging tools include correct merging across renamed directories
One Con
UCM makes it hard to prune history
|
|
|
|
|
You forgot the other con...
It's horrible!
|
|
|
|
|
We currently use SVN at work, but even there we're looking at moving to Git. Possibly using Github at that.
Interesting to see that SVN still has some lead though!
Er, I can't think of a funny signature right now.
How about a good fart to break the silence?
|
|
|
|
|
If you are a small organisation and development environment is very dynamic and lot of small experiments you are doing go with GIT or HG.
If you are ready to spend money in TFS no doubt you can use it for any purpose, but then ask do you really need that investment.
|
|
|
|
|
Hi Gary!
"and I use Visual SourceSafe."
Software Zen: delete this;
|
|
|
|
|
God bless your code, and all who sail in her...
Er, I can't think of a funny signature right now.
How about a good fart to break the silence?
|
|
|
|
|
Truthfully, we've used SourceSafe for 13 years now, and never had a data loss due to SourceSafe itself. We've had server disk failures and other sorts of disasters. That said, one of my back-burner projects for this year is to find us another source control solution. We're going to be upgrading our development from VS2008 to VS2013+ during that time, and I sincerely doubt VS2013 supports SourceSafe any longer.
David Lumm wrote: God bless your code, and all who sail in her...
Fortunately our products don't have any health or safety implications, other than the possibility of one hell of a paper cut (we build commercial ink-jet printers).
Software Zen: delete this;
|
|
|
|
|
Don't worry, I was joking! Well, not about my face. It still made me feel a bit queezy! lol! But congrats on using any piece of software relatively successfully for 13 years, especially one from Microsoft!
My previous employer used VSS then moved to TFS and then slowly transitioned to Git. Now I'm using SVN at work but we're probably also going to Git in the next year or so.
The "problem" with Git is that it can be complicated, but as others have mentioned, Github makes a lot of the process much easier. But then again, so can any good GUI tools!
Er, I can't think of a funny signature right now.
How about a good fart to break the silence?
|
|
|
|
|
Git does seem to be very popular at the moment. I'll take a look at it, but I have a number of 'problem children' in my group when it comes to source control. The complexity attributed to Git will probably be an issue, unless I can find a client that makes things simple.
Software Zen: delete this;
|
|
|
|
|
Gary,
we found the transition to SVN awkward at first (VSS teach BAD concepts, like locking). But it took only a
couple of DAYS once we found the Repo Browser and TortoiseSVN for shell integration... We were 80% and we simply
had to work through the branching/merging.
Do yourself a favor... Figure out your "structure" and add an EXTRA directory, like "trunc" to the FRONT of your
repository path. Actually just play with it for a couple of days, and try to get your branches straight. Like most things, by the 3rd time you load everything into SVN, you become pretty good at it.
Our original hiccups were: branches/ (did not set it up for it), and projects in multiple languages, which in the end we created as the initial set of paths (websource/ delphi5/ delphiXE/ vs2010/ ), then we did the branches.
and true to form, we meet people with 5yrs of SVN experience, that really have 1 month of SVN experience for 60 consecutive months. LOL. (No idea how to branch, merge, or even really compare 2 different versions without a switch).
Good Luck...
PS: I have held back on Git only because SVN is doing it for us, and we support numerous clients who we put on SVN... Change becomes hard...
|
|
|
|
|
Thanks for the suggestions; I'll keep those in mind.
Software Zen: delete this;
|
|
|
|
|
Complete the sentence please.
Gary Wheeler wrote: Hi Gary!
"and I use Visual SourceSafe. Writing VB6 code on XP machine & use browser control to simulate IE6"
FTFY 
|
|
|
|
|
I've never written any Visual Basic, much less VB6.
Until recently, I did develop on an XP box; our legacy products still run on it, so developing on it made sense.thatraja wrote: use browser control to simulate IE6
Is this somehow supposed to be related to my article Using the WebBrowser control, simplified[^]? I'll admit the article is a little dated, but I did polish it up a couple years ago. It's seemed fairly popular, and not too many folks have down-voted it.
Software Zen: delete this;
|
|
|
|
|
Oh no. I just mentioned couple of outdated things there(VB6, XP, IE6.,). Too bad CM & co removed joke icon here so my joke message is
Gary Wheeler wrote: It's seemed fairly popular, and not too many folks have down-voted it.
Please check mine there.
|
|
|
|
|
Thanks for the 5!
Software Zen: delete this;
|
|
|
|
|
Do you have the other half of this medallion?  And I have even used your web browser control in a project. I used it for making a generic dialog as I got sick of creating common dialog resources just for presenting some data. With your little class I can tag on some styling and HTML formatting - works great.
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
I'm glad you like it. I've used it a lot for displaying HTML I've generated for reports and such.
Software Zen: delete this;
|
|
|
|
|
Yeah, that is kind of what I do to.
As a side project, I used it with styling to create a MessageBox() lookalike dialog. It was really just to see if I could do it, but it actually makes it possible to stick all kinds of things in a MessageBox (tables, images, you name it).
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
I think there's something to be said for it. I've probably used that more than anything else over the years, but not for 10 years at least now.
In those days, when someone had a file checked out a verbal 'after you' seemed to work ok. Now we have branches everywhere and horrendous merging, one of the most painful parts of my job.
Whilst I accept that this is the way things work these days and I wouldn't go back it did seem to work just fine in the old days.
Regards,
Rob Philpott.
|
|
|
|
|
Our group is small. When we first started out, we decided the exclusive checkout model was easier for us to deal with. It's become part of our 'culture' now. We do use branching, but it tends to be a 'whole product' kind of thing. When a version is released to manufacturing, we create a branch for maintenance purposes. It becomes a separate development path for the software. Usually there are only a few updates in the branch, but we've occasionally had active branches that were maintained for years (stern looks  at certain customers who refuse to update to later versions).
Software Zen: delete this;
|
|
|
|
|
Good Lord.
Guys, can we have a whip round?
|
|
|
|
|
The key here is to learn to love the whip.
Software Zen: delete this;
|
|
|
|
|
I used Git, CVS and Mercurial (Hg) before.
and I like Mercurial (Hg) more.
Mercurial (Hg) is more easy to handle.
|
|
|
|
|
Not really programming in high level last time, but when... I use to do backups each day with timestamp in name and a tiny explanation on what was going on that day. If I need more explanation then I add a tiny *.txt with what I need to save.
If I come back to high level end, I suppose I will have a look to those tools and pick one.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
you should use some scc to aquire the knowledge. I would recommand git
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
