What Source Control and issue tracking system would you choose today?
-
Yes, I know the question has been asked before, but things change and so does opinions. I have finally been tasked with exchanging our stone age CVS system and to implement an issue tracking system at the same time. ... And I just removed half a book of what I've looked at and how I reason about my choices, because I realize that I should get your "unbiased" opinions. :rolleyes: <edit>We're a small shop doing mainly Asp.Net and forms with Oracle as backend DB</edit>
Wrong is evil and must be defeated. - Jeff Ello
We use JIRA and SubVersion; and will be soon using the Crucible (codereview) and FishEye (code tracking) JIRA plugins.
I'd rather be phishing!
-
Yes, I know the question has been asked before, but things change and so does opinions. I have finally been tasked with exchanging our stone age CVS system and to implement an issue tracking system at the same time. ... And I just removed half a book of what I've looked at and how I reason about my choices, because I realize that I should get your "unbiased" opinions. :rolleyes: <edit>We're a small shop doing mainly Asp.Net and forms with Oracle as backend DB</edit>
Wrong is evil and must be defeated. - Jeff Ello
Really depends on the team, their size and skill-set, the project, etc. Recently I decided to go with SVN for a project, mainly because I need both *Nix and Win support and nobody else where I work has *Nix experience, and I'm not using VS to develop it. Once git gets better Windows support I'll switch over to that. If I were in a large corporate environment again, with a bunch of MS devs using VS, I'd be tempted to stay with TFS. That unless until MS increases their git support in VS too, in which case TFS goes bye bye along with SVN.
Jeremy Falcon
-
Yes, I know the question has been asked before, but things change and so does opinions. I have finally been tasked with exchanging our stone age CVS system and to implement an issue tracking system at the same time. ... And I just removed half a book of what I've looked at and how I reason about my choices, because I realize that I should get your "unbiased" opinions. :rolleyes: <edit>We're a small shop doing mainly Asp.Net and forms with Oracle as backend DB</edit>
Wrong is evil and must be defeated. - Jeff Ello
I really do not know why anyone would use anything other than TFS unless they are cutting costs.
Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet. The interesting thing about software is it can not reproduce, until it can.
-
Yes, I know the question has been asked before, but things change and so does opinions. I have finally been tasked with exchanging our stone age CVS system and to implement an issue tracking system at the same time. ... And I just removed half a book of what I've looked at and how I reason about my choices, because I realize that I should get your "unbiased" opinions. :rolleyes: <edit>We're a small shop doing mainly Asp.Net and forms with Oracle as backend DB</edit>
Wrong is evil and must be defeated. - Jeff Ello
Anything but TFS. It's not bad, it's just very lackluster.
Curvature of the Mind now with 3D
-
Yes, I know the question has been asked before, but things change and so does opinions. I have finally been tasked with exchanging our stone age CVS system and to implement an issue tracking system at the same time. ... And I just removed half a book of what I've looked at and how I reason about my choices, because I realize that I should get your "unbiased" opinions. :rolleyes: <edit>We're a small shop doing mainly Asp.Net and forms with Oracle as backend DB</edit>
Wrong is evil and must be defeated. - Jeff Ello
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.
-
How many developers ? What target technology ? How many location (including writing tickets, reading tickets, development, testing, etc...) ?
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus Entropy isn't what it used to.
We're a very small shop with an IT department that just shrunk to below ten people, but the number of people that should be able to write tickets counts in thousands. We're exclusively doing Visual Studio for the foreseeable future.
Wrong is evil and must be defeated. - Jeff Ello
-
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.
SVN lacks tools for proper Source Code Management.
-
Yes, I know the question has been asked before, but things change and so does opinions. I have finally been tasked with exchanging our stone age CVS system and to implement an issue tracking system at the same time. ... And I just removed half a book of what I've looked at and how I reason about my choices, because I realize that I should get your "unbiased" opinions. :rolleyes: <edit>We're a small shop doing mainly Asp.Net and forms with Oracle as backend DB</edit>
Wrong is evil and must be defeated. - Jeff Ello
-
Yes, I know the question has been asked before, but things change and so does opinions. I have finally been tasked with exchanging our stone age CVS system and to implement an issue tracking system at the same time. ... And I just removed half a book of what I've looked at and how I reason about my choices, because I realize that I should get your "unbiased" opinions. :rolleyes: <edit>We're a small shop doing mainly Asp.Net and forms with Oracle as backend DB</edit>
Wrong is evil and must be defeated. - Jeff Ello
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.
-
SVN lacks tools for proper Source Code Management.
-
I really do not know why anyone would use anything other than TFS unless they are cutting costs.
Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet. The interesting thing about software is it can not reproduce, until it can.
That's a good enough reason for many companies.
Wrong is evil and must be defeated. - Jeff Ello
-
Anything but TFS. It's not bad, it's just very lackluster.
Curvature of the Mind now with 3D
Would you mind expanding that?
Wrong is evil and must be defeated. - Jeff Ello
-
I'm doing that too, it just feels a bit limited.
Wrong is evil and must be defeated. - Jeff Ello
-
We use JIRA and SubVersion; and will be soon using the Crucible (codereview) and FishEye (code tracking) JIRA plugins.
I'd rather be phishing!
Are you happy with Jira? Any specific gotchas?
Wrong is evil and must be defeated. - Jeff Ello
-
Thirded
I'm seeing a pattern here. Are you at a big company?
Wrong is evil and must be defeated. - Jeff Ello
-
I'm seeing a pattern here. Are you at a big company?
Wrong is evil and must be defeated. - Jeff Ello
Been at very large and now at reasonably small. Have used many different systems over the years but have found TFS to best fit the need. What really helps has been getting a TFS consultant in to make sure the system is set up so as to best serve our needs.
-
Yes, I know the question has been asked before, but things change and so does opinions. I have finally been tasked with exchanging our stone age CVS system and to implement an issue tracking system at the same time. ... And I just removed half a book of what I've looked at and how I reason about my choices, because I realize that I should get your "unbiased" opinions. :rolleyes: <edit>We're a small shop doing mainly Asp.Net and forms with Oracle as backend DB</edit>
Wrong is evil and must be defeated. - Jeff Ello
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
-
Are you happy with Jira? Any specific gotchas?
Wrong is evil and must be defeated. - Jeff Ello
The switch was made a couple of weeks ago; we used an in-house system (MS Groove workspace) and had a good process workflow that we were not able to completely reproduce with JIRA, mostly because of different mentality. JIRA is working nicely for end-users; logging work and adding comments is simple and straightforward , and our manager (a good one) is happy with all the reporting and management tools. One thing is that by default, JIRA will sent TONS of emails; so you have to configure it properly (system and per user). we are about to integrate Crucible for code review, I did not try it yet, so I cannot comment about that
I'd rather be phishing!
-
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
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.
Wrong is evil and must be defeated. - Jeff Ello
-
Really depends on the team, their size and skill-set, the project, etc. Recently I decided to go with SVN for a project, mainly because I need both *Nix and Win support and nobody else where I work has *Nix experience, and I'm not using VS to develop it. Once git gets better Windows support I'll switch over to that. If I were in a large corporate environment again, with a bunch of MS devs using VS, I'd be tempted to stay with TFS. That unless until MS increases their git support in VS too, in which case TFS goes bye bye along with SVN.
Jeremy Falcon
Jeremy, TFS includes Git based version control. I have just discovered this at my new position, where TFS seems the de facto, but I was very pleased to learn that this still boils down to Git.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde