Re: NewEra: Team Development, How?

In article <4ku03m$hs7@cssun.mathcs.emory.edu>, m.mejia@server1.codetel.net.do says... > >Hello Informixers: > >I've been developing an client/server application using I-NewEra, and I >would like to hear some opinions about developing with a develpment team > >I haven't purchased PVCS, I'm evaluating, because I'm stuck in the sharing >problems. Now, I'm using WFW resources, but I don't think that this is the >best way: there's a computer with all the source code and the developers >refers to this path. The first computer serves as a application server, in >which all the components source code is written. > >If you're developing using NewEra for Windows, with a development team, how >are you addressing this problem? > >Any alternative to WFW? > > We had the same problems with team development. Starting off on our first project, each developer used a local machine for coding. Changed files were manually promoted to a network file server where a release build was performed. This proved to be inadequate as the project progressed and the number of code modules increased. The ideal solution is to check in all the source on the file server and check out code to the local machine. Due to a bug in NewEra (mentioned previously by dwc), this is impossible as it duplicates include dependancies if referenced files are located on different machines. The only other solution is to replicate the source archive on each local machine with periodic consistency updates. I am currently evaluating PVCS to manage the source code control. Could someone report on how well it has integrated with NewEra and team development? Has it successfully contributed to the development project and if so, how? TIA, Ciaran Kelly RTE Engineering Software email: kellyci@rte.ie