|
Collin Jasnoch wrote: By that I mean the argument for it depends on the business model
I don't understand that statement.
I have experience in a wide swath of environments including very large to very small companies, different process models and different industries.
So is there a specific example of some business model and a specific feature of this tool that you can specify and tie together.
|
|
|
|
|
Anything but TFS. It's not bad, it's just very lackluster.
|
|
|
|
|
Would you mind expanding that?
|
|
|
|
|
TFS has basic issue tracking, but configuring fields and changing allowed statuses requires exporting xml, editing it and importing it.
Each project has a template for how issues are tracked, but changing templates midstream can be a pain, and some features aren't available for all templates. Upgrading major versions of TFS can be a pain, and synchronizing the 5 databases to get clean backups requires a custom script.
The source control portion is better now, and you don't have always be connected to the TFS server without it complaining. However, TFS is lacking things like being able to search for commit messages. The file search will only search by file name not file content.
Branching and merging work just like other systems and I haven't had any issues with any of the basic operations. However, it can support something like a 20 server configuration with multiple database servers, web servers, sharepoint servers, and custom source proxy servers for handling remote offices, so it can definitely scale up to handle something as huge as the windows codebase.
|
|
|
|
|
Thanks!
|
|
|
|
|
Andy Brummer wrote: However, TFS is lacking things like being able to search for commit messages.
WAIT WHAT THE SHEEP? Just... can't?
Now, I'm sure you could open the relevant DB and fire a query at it
|
|
|
|
|
There are plugins that do that now, but the early recommendation was to export all the comments to a text file and then search the file.
|
|
|
|
|
Holy moly.
First surprise in this thread was the strong support for TFS, second surprise was your comment.
As much as gitk's search is awkward, it's at least functional (search for: commit ID, comment, file names in the change set or changes in the source)
[edit] Locating a particular commit is now intrinsic part of our workflow, but maybe one usually doesnÄt do that in TFS that often.
|
|
|
|
|
I still like SVN even it is also Little bit Stone Age (but still widely used) and tortoise for Windows still Show a lot of misleading Status Information in Windows Explorer. But when one knows the "special" tortoise behaviour one can live with it.
I don't know TFS but can imagine it is most valuable tool for visual Studio and worth to have a closer look to it.
modified 19-Jan-21 21:04pm.
|
|
|
|
|
SVN lacks tools for proper Source Code Management.
|
|
|
|
|
Once again most probably a lack of my english. Seems I did not understand the question enough.
Sorry
modified 19-Jan-21 21:04pm.
|
|
|
|
|
You can use add-ons that work with SVN to help with that. That's the nature of OSS, it's all distributed. Whereas MS puts it all in a box and shrink wraps it for you.
Jeremy Falcon
|
|
|
|
|
USB drive.
|
|
|
|
|
I'm doing that too, it just feels a bit limited.
|
|
|
|
|
Jörgen, why not use TFS online (hosted at MS) for free? I've been using it for my personal projects and absolutely love it!
/ravi
|
|
|
|
|
Is it free for business too?
|
|
|
|
|
Yessir, for up to 5 users!
/ravi
|
|
|
|
|
Damn, but good enough for testing actually.
|
|
|
|
|
Source control would depend on the project.
For a really large code base - Perforce.
For an open source project - Git (because of GitHub)
Most other cases - SVN.
As for the tracking system, I've tried a few and all are horrible: Jira, Bugzilla, Trac.
|
|
|
|
|
Moving from something ancient like CVS probably SVN. Much smaller learning curve than a distributed system.
Never used TFS so no comment.
TortoiseGIT is a clunky cluster elephant compared to TortoiseSVN. All my git work has been for Ruby so no comment on VS's git integration.
I've used mercurial for a few small personal projects, chosen mostly on the fact that whenever I read a git vs hg article I inevitably found myself in agreement with hg, but I haven't used the latter enough to make any judgments about largescale use. It's been long enough since I did the reading that I don't recall any specifics beyond GIT was all "MOAR POWAR!!!!!" while Hg tried to keep you from shooting yourself in the foot by accident (but if you really decided paying a doctor to amputate that toe was too expensive there was a way to do it).
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
modified 25-Nov-14 9:50am.
|
|
|
|
|
I believe you've been reading the same articles as me.
Before this post I were leaning towards Mercurial, but enough people have mentioned TFS that I will have to take a serious look at it. I'm having a soon former workmate that's been working with it that recommended against it for price/performance reasons or rather just price reasons.
|
|
|
|
|
VSS and Access
it worked in 1998, it can work today!
|
|
|
|
|
I don't have any memories of either of them working.
|
|
|
|
|
TFS for source control, and most likely TFS for work item and issue tracking, since it integrates seamlessly with source control.
/ravi
|
|
|
|
|
I use FogBugz for issue tracking and VisualSVN (on my own server) for source control
|
|
|
|