<tongueInCheek> Is this something that StarTeam does? </tongueInCheek>
-----Original Message----- From: Richard Vowles [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31 2004 11:32 a.m. To: NZ Borland Developers Group - Delphi List Subject: RE: [DUG] Source code control It should also be about tying them back to (a) change requests and (b) requirements, but that is a bigger discussion :-) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dennis Chuah Sent: Wednesday, 31 March 2004 11:15 a.m. To: NZ Borland Developers Group - Delphi List Subject: Re: [DUG] Source code control I would disagree. Rolling your own is a bad idea. Source control is not only about comparing versions and storing files away. There is also tracking changes in source code (hopefully with useful comments per version), branching code (so that you don't screw up your customers by adding new functions for the next release), controlling access (which in Eric's case is irrelevant because he is the only developer), keeping versions (so that you can roll back code when necessary), etc. Better to use a dedicated source control product for this. _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
