Suggestions as a single developer looking to start SCC

[Stranman]

Looking for suggestions as a single developer looking to start Source Code Control?

I’ve been developing code since 7.1 (currently in 2009), but recently after reading various articles, etc. have concluded I should be using SCC of some type.

I keep all my code organized in a single folder w/ my programs organized based on the Job they’re written for as the main folder containing all upper level vi’s and a subfolder “support_vis” containing all subvi’s.

C:\LV\JobA  with   C:\LV\JobA\support-vis

…

C:\LV\JobZ

Up till this point, I’ve documented my code using the “Documentation” and “revision history” properties.

I tend to practice code re-use, but run into problems trying to remember if I’m actually using the latest subVi for the function I’m looking to use. (was it JobA, JobC, or JobX subvi I want to use?)

I’m looking for suggestions on getting started, lessons learned, SCC you use, etc. I understand this is quite a can of worms, but after reading thru various ni software dev links, I’m simply over-whelmed on which direction to go (Perforce/TortuiseSVN), etc.

[F._Schubert]

Short answer:

Get the SVN tortoise 1-Click Setup and start using it.

Edit:

Not so short answer:

Use a central reuse repository if you want to use the latest Support VIs for the next project and the External flag to keep the old revision for the old JobA. JKI has a blog post about that setting. Also consider using a bug-tracker and link it to revision numbers if you need support for an older project and need to know which bug was fixed in which revision. But I can't recommend an easy to setup tracker, they all require some SQL/Python/Server skills.

Felix

Message Edited by F. Schubert on 03-23-2010 03:38 PM

[Mark_Yedinak]

I am in complete agreement with Felix.

[smercurio_fc]

I agree that SVN is a good place to start. Note that TortoiseSVN includes what you need to access a repository, but if you want to set up a true server then you will need to get Subversion and install it on a server. I'd suggest going with CollabNet or Visual SVN Server (which is what I use). The latter seems to be geared to simple installation and configurations. The former seems to be for a more "get down to the nuts and bolts level" operation.

[Jim_Kring]

For Bug Tracking, sign up for a free (for up to two users) FogBugz Students and Startups account.  And, if you can afford $30/month, get the a full on-demand account with integrated Kiln Mercurial (a.k.a "Hg") source code control.