Re: NewEra: Team Development, How?

> 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 > using NewEra. I know that Informix recommends to use PVCS for those > features, but I still confused about sharing application components. > 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. That setup was our original configuration but we have gone through a number of different configurations. A brief summary follows: 1. All source on one network directory and code is edited in that directory. This is fine for two developers but with 20, it is painfully slow when compiling. If someone changes a header then everyone will suffer. 2. All checked-in source is on the network directory and checked-out source is on the developer's local PC. Benefits are fast compiles and less interference however header changes are still a nuisance. There are also problems with the mismatch of headers on the local PC and the network drive. We originally logged this as a NewEra bug but unfortunately it was a Microsoft Visual C++ problem. 3. All checked-in source is on the network directory and each developer keeps a complete copy. This was very good because developers could work without interference from others and compiles were very quick. The problem was that every day, each developer had to refresh the source from the network directory. Checked-out files were not a problem because PVCS looked after that. 4. Same as 3 but also have a central integration machine where we would do a build from PVCS once or twice a day using the latest versions. This saved on each developer having to recompile since they could take the files from the build machine. This is what we still use now. We have also stopped using PVCS from the application builder and use the DOS commands because they are fast. In general PVCS is very good and the use of promotion groups is a godsend. I wish SCCS had that. There are about 20 developers here building one system and the configuration we have at present is both flexible and convenient to use. We don't use the PVCS WIndows executables anymore because they are very slow. We use the DOS commands instead which give you access to all the functionality. > ////// > +---------------------------ooo-O-O-ooo--------------------------------+ > | U | > | Melvin Perez Cedano Santo Domingo, Dom. Rep.| > | Vice-President m.mejia@codetel.net.do | > | Systems Development Phone (809) 686-5574 | > | CAM Informatica, S. A. Fax (809) 686-5467 | > +----------------------------------------------------------------------+ > | ALL RIGHTS RESERVED | > | This posting is copyright and may be used only for the purposes | > | of professional study or the professional exchange of information. | > | Use of this posting by any commercial organisation for the | > | purposes of vilifying another is explicitly prohibited. | > +----------------------------------------------------------------------+ > > David W Chan GO5 Limited dwc@cix.compulink.co.uk