David You might want to check out an article I wrote for Spectrum about this. Back-issues are on www.intl-spectrum.com.
One other tip: We used CVS at my last company, which was quite a complex arrangement handling server and client side code (and keeping these in sync). The key was to appoint someone who was responsible for it. If it is anything more than trivial, it needs someone charged to administer it, not just left to the whims of developers! That was the best decision we made... Regards Brian > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David Beahm > Sent: 16 April 2008 21:22 > To: [email protected] > Subject: [U2] version control > > We are looking to add our UniData/SBClient environment to > Subversion, and wanted to get advice from anyone who has done s > something similar (CVS, etc.) Searching through past posts, > I found Brian Leach's note about generating DICT items from > scripts, which I quite like; I suspect there are more ideas > like that around. > > First, however, we need to come up with a suitable repository > structure. We have a number of live, proto, and development > accounts on one box (HP-UX). We have some universally shared > directory files, but most files are unique to each account. > > To begin with, we are wondering whether it would be best to > have individual repositories for each account, or whether > there should be one repository with relative paths for each > account, or whether each account should be a different branch, etc. > > Suggestions welcome, however we are want to standardize on > one solution > -- Subversion. > > Thanks, > David Beahm > ------- > u2-users mailing list > [email protected] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
