Author |
Topic |
tbrothers
Yak Posting Veteran
83 Posts |
Posted - 2010-11-01 : 16:00:56
|
Hello,We have 4 programmers that are going to be working on a very large project over the next 2 years and we are in need of a code repository. We would like to store, share, check-in/check-out, etc.I have looked at Team Foundation Server but my initial thought is this is way over-kill (requires SQL and SharePoint). But since we have never used a repository before I can't say for sure.Any suggestions?If I posted this in the wrong area, please forgive me.Regards,Terry |
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
tbrothers
Yak Posting Veteran
83 Posts |
Posted - 2010-11-01 : 16:18:30
|
I don't mind purchasing a product as long it's decent. I just want something that'll provide the necessary functionality ... but without the bloat that you get with a lot of products.Thanks,TerryThanks,Terry |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
robvolk
Most Valuable Yak
15732 Posts |
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2010-11-01 : 16:22:02
|
You could also check out (hehe, I crack myself up):http://www.sourcegear.com/vault/It's not free for team/corporate use but it's a lot cheaper than TFS. |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-11-01 : 16:37:10
|
We have used Subversion and Tortoise (front end tools for Windows) for years and are very happy with it. People seem to say they are changing to GIT instead. I haven't figured out why though (and maybe its more Talk than Action anyway)Make sure you experiment with Branches before doing any serious checking in of real code. You can wind up with lots of sub-folders of variations of your source code, under your "checked out" folder, and its good to get that sorted out / understood whilst you are still at the "wipe the repository and start over" stage Links to somewhat dated discussions (below), but I think still relevant (particularly discussion around Checkout-and-lock (which we hate here) and Change-anything-you-like and then resolve-conflicts-at-checkin (which we like, and in reality very rarely have a check-in-conflict - well, if we don't checking for Months we would have conflicts, but checkin-often is a good strategy for all sorts of reasons. Not least of which is that checkin-when-you-like works well if you are working on a laptop away from the office - you have all source code with you, you can view / edit anything, and just check it in when you get back to the office. Who wants to be using Checkout-and-lock with a 4G card on a Mobile phone at 40,000 feet?!http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=61248http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=63148"working on a very large project over the next 2 years"Other things you may want to aim for:Automated Daily buildAutomated regression testFirst job of the day: fix bugs found overnight on yesterday's code. Its still fresh in your mind what you did/changed yesterday that caused the problem, and you haven't yet written a ton of code that depends on the method you built yesterday that now turns out to be buggy. The alternative of "build code for months and then try to remember what you did when debugging reveals bugs" is a complete PITA and a huge project-timeline-killer.Aggghhhhh, what am I doing trying to explain this? people like Joel Spolsky describe this stuff far better than I ever could. See how you fair on "The Joel Test":http://www.joelonsoftware.com/articles/fog0000000043.htmlIMHO you absolutely need 1-5, and 12 (plus automated regression test above); I figure that even bad code shops have enough within 6-11 to get by :) |
|
|
AndrewMurphy
Master Smack Fu Yak Hacker
2916 Posts |
Posted - 2010-11-02 : 04:25:40
|
And talking about Joel....have a look at his Repository product. Web based & low cost.http://www.fogcreek.com/Kiln/ |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-11-02 : 04:32:35
|
In which case might as well use his Bug Tracking tool too Free for 2 users or less - ideal for small projects.http://www.fogcreek.com/fogbugz/ |
|
|
|