was Source Control Choices

2006-02-24 Thread Michael Traher
Since this topic crops up regularly and I have started a series of posts on my blog to help in this area. The posts will cover my experience in setting up and using CVS for a Coldfusion team which comprises over 25 developers, spread over offices in the UK, India, Singapore, Hong Kong and Sydney,

Re: Source Control Choices

2006-02-22 Thread John Paul Ashenfelter
On 2/21/06, Michael Traher <[EMAIL PROTECTED]> wrote: > SVN is the next generation of CVS and has fixed some CVS limitations so this > is worth a look. And specifically for VSS folks, SVN now supports locking (VSS-style one file/one developer) checkout as well as the more common in CVS/SVN concur

Re: Source Control Choices

2006-02-21 Thread Douglas Knudsen
yeah, on the whole my company uses Dimensions, a very expensive product with a learning curve. My team is a bit of a rebel child and we use CVS with TortoiseCVS as a CVS client. Free, well known, and with TortoiseCVS easy to use. Now to get the team on Eclipse, CVS support in Eclipse is uber sch

Re: Source Control Choices

2006-02-21 Thread Robert Munn
My company uses Perforce, which has a little learning curve but is a very cool product that supports everything you are looking for and more. Well worth a look, but unlike CVS/SVN, it is a commercial product. > What we are looking for is something that makes the release process > from server t

Re: Source Control Choices

2006-02-21 Thread Michael Traher
replies below On 2/21/06, Neil Middleton <[EMAIL PROTECTED]> wrote: > > >So each PC has cf developer edition and IIS under WXP pro. > > How do you go about keeping these all up to date? How do you manage more > than one developer working on an app at any one time. Well the CVS repository holds a

Re: Source Control Choices

2006-02-21 Thread Neil Middleton
>So each PC has cf developer edition and IIS under WXP pro. How do you go about keeping these all up to date? How do you manage more than one developer working on an app at any one time. >CVS handles branching and it is made easy to manage by the tools in eclipse. How do you handle branching f

Re: Source Control Choices

2006-02-21 Thread Michael Traher
Hi Neil, This crops up regularly on this list so a search of the archives may be prove fruitful for you. We use CVS because our IDE of choice is CFEclipse and the CVS integration is part of the base eclipse product. We too have very large systems and several of them (although probably not as big as

Source Control Choices

2006-02-21 Thread Neil Middleton
We're looking at changing our source control system but are having trouble finding something that seems suited to our needs. Basically, we have around six developers all working on our applications, checking into a dev server with VSS before running the code. From here the code goes to a test