We use CVS here. All file size info, dictionaries, VOC pointers, and other source code are checked into CVS. Artifacts that can be generated from source code are left out.
TortoiseCVS is a windows client for CVS that makes it easy to look thru the scc library. If I had to do it all over again, though, I'd opt for using Subversion and TortoiseSVN). When using any source code control system, it's important to have a one-step build process to checkout all the source code and generate a complete system (for testing or distribution.) Too often, someone needs to slip in "just one more fix" and if the build process has a lot of steps (or heaven forbid, manual steps) tasks get skipped. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > [EMAIL PROTECTED] > Sent: Thursday, September 29, 2005 2:11 PM > To: u2-users@listserver.u2ug.org > Subject: [U2] Source Code Management > > > All, > > The thread regarding the "good programming practices" and comments > regarding versioning raised some questions for me. > > What tool are you using for source code management? What are its > benefits and disadvantages? I'm specifically interested in version > control....preferably Unix-based. If you have vendor > information, please > provide that as well. > > In a previous life, I used something called sccs - I don't > know if it's > a current offering in the marketplace? > > > Thanks!!! > > Karen Bessel > Programmer/Analyst > Ferguson Enterprises Inc. > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
